Tag Info

New answers tagged

2

I am presented with SMB, NFS and iSCSI options to connect to the server. Meaning, I have the option of either setting up a share via NFS or SMB or creating a virtual iSCSI drive in which I can connect to. For direct connection to a server—for true server related storage—iSCSI is the way to go. And you would then manage the user access—via SMB/CIFS ...


1

When you say you are presented with those option to connect to the server, what are you referring to? For HyperV, you most likely would use a locally hosted VHD(x) file on local exposed drive in the Hosts's OS. There are reasons to do some of the other methods like iSCSI, but typically they are for use cases where you need clustering or failover or have ...


1

can I have two LUNs from the same SAN attached to the same server Yes, easily - glad you checked though!


1

Simple answer: yes. This is done all the time - there's nothing preventing multiple LUNs (either FC or iSCSI) from one SAN going to the same server. As an added twist to the simple answer: if you have one LUN going to multiple servers, you will have to ensure you either have only one server mounting it read/write or that you have a multi-initiator capable ...


0

The key to answering this question was to enable logging of errors in ietd, which isn't enabled by default for some reason. I stopped the service with /etc/init.d/ietd stop, and manually ran ietd -d 2 to get logging turned on. This gave me (along with a whole load of extra junk) the following error message: Feb 17 17:15:50 athena ietd: unable to create ...


1

Mechanical HDDs struggle at random I/O access. 4x WD Green that give you 5 MB/s of random read performance is even better than I expected.Some math: at 5400 RPM, a single rotation need 11 ms, so an half-rotation need ~5.5ms. This is the rotational delay. Adding another ~8ms of seek time (the time the actuator needs to correctly position the read/write heads) ...


1

This configuration has a lot of components and design decisions that contribute to its poor performance. The HP Microserver is low-performance item. RAM-constrained and low-end CPU. Western Digital Green drives are low-RPM and require special consideration for their 4k-sector formatting. This is likely the main problem. It seems like you may be using ...


0

The problem was that the multipath blacklist in /etc/multipath.conf had been amended to exclude /dev/sda1: devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|sda|sdb|sdc)[0-9]*" The regex above catches /dev/sda1 as intended, but it also catches /dev/sdaa1 and /dev/sda_foobar. To fix, amend the blacklist to include the end of the device name: devnode ...


0

The problem was caused by a machine which heartbeat in the cluster although it should have been detached from it. Weird error message, though.


1

You can leave these 'discovered unavailable' targets there, the initiator can't login to these targets. However, these 'unavailable' targets will slow down the initiator start/stop time, so it would be better just remove them. You will find all discovered targets in /var/lib/iscsi/nodes, so run rm -rf ...


0

Added the following to /etc/cinder/cinder.conf on the storage node: [DEFAULT] enabled_backends=lvm57 [lvm57] iscsi_helper=lioadm volume_group=cinder-volumes volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver iscsi_ip_address=192.168.186.168 volume_backend_name=LVM_iSCSI ...



Top 50 recent answers are included