iSCSI and LVM: Boot problem

Both LVM and iSCSI are powerful and reliable. But there is an issue with the combination of both that made me fell completely lost more than once.

The Scenario:
iSCSI target / server is a Linux Box with LVM features
iSCSI target / server exports disk, partition or LVM LV
iSCSI initiator / client uses the exported volume as LVM PV
All works perfectly until rebooting the iSCSI target / server

The symptom:
After rebooting the iSCSI target / server, it becomes impossible for the initiator / client use the exported volume as if it were deleted. The iSCSI target / server service itself is working properly but the exported volume is not.

The cause:
During the boot of the iSCSI target / server, its LVM liked the new found PVs / VGs / LVs. The iSCSI target / server has no idea about those new found are not for the local machine and it "locks" the VGs and LVs for local use. When iSCSI exports the LV, it will contain locked LVM volumes. This is why it becomes impossible to use it on the iSCSI initiator / client.

The solution:
It is very easy. Edit /etc/lvm/lvm.conf and use "filters" to tell LVM what is not for local use. My filter is configured as:

filter = [ "a/sda/", "r/.*/" ]

For testing, just type pvscan after editing the file to see if the filter worked as expected. If so, just reboot and it will work.

Please note that using sda on the filter is not the safest solution as it is not impossible that sda becomes sdb for example. It will be safer to use UUIDs of something else.

Comments

Anonymous said…
Thank you, this resolved my issue with running: `/usr/sbin/tgt-admin -e` and it failing: "exited with code: 72057594037927935." In addition I would see tgtd segfault in demsg. Also my LUN would never show up (after rebooting the server) when I ran `/usr/sbin/tgtadm --lld iscsi --op show --mode target` until I added the LVM filter and rebooted.
Wed Mar 20, 02:38:00 AM GMT-3
Post a Comment

Popular posts from this blog

Toshiba R830 and 16GB of RAM

Image
The datasheet of Toshiba R830-10P mentions that the maximum memory capacity is 8GB. See it  here . But Intel says that the i7-2620M supports up to 16GB of RAM. See it here . I have asked for help on Toshiba Forums. Nothing useful from there. See it here . I was curious as I have a very particular need for 16GB of RAM. Today I decided to give it a try. I bought two Patriot PSD38G13332S (8GB PC3 - 10600 1333MHz CL9 SoDimm) and installed it on the notebook. It just worked. So if you have the need for 16GB of RAM and a similar notebook from Toshiba, you can install 16GB of RAM.
Read more

Five steps to create Fedora chroot jail using yum

Pre-Notes: - This will work only if your Linux Distro is based on RPM and YUM. I have tested it on Fedora but it may also work on RHEL and Centos... It will NOT work on Ubuntu, Debian, Suse... - The operating system and its version will be the same inside and outside the chroot jail. - On the example, the chroot will be placed at: /chroot/devel - To install different version of Fedora or other RPM based distro, it will be necessary to manage yum package repositories outside the jail. The five steps: # 1 - Create the chroot directory $ sudo mkdir -p /chroot/devel/var/lib/rpm # 2 - Initiate rpm db on chroot $ sudo rpm --root /chroot/devel --initdb # 3 - download Fedora Release package. # If you do not want Fedora, download the correct *-release package and use it # on step 4. There are examples on the references. $ yumdownloader --destdir=/tmp fedora-release # 4 - Install downloaded Fedora release inside chroot $ sudo rpm --root /chroot/devel -ivh /tmp/fedora-release*r...
Read more

How to recompile software with hardware optimization?

This may be useful for compiling local applications that you want to run faster. Try this on your computer: $ echo "" | gcc -march=native -v -E - 2>&1 | grep cc1 On my computer it has returned:  /usr/libexec/gcc/x86_64-redhat-linux/4.6.1/cc1 -E -quiet -v  - -march=corei7-avx -mcx16 -msahf -mno-movbe -maes -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm -mavx -msse4.2 -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=4096 -mtune=corei7-avx This command probes the local computer for optimization flags. To use it: $ CFLAGS=" [blue string from above] " ./configure You may consider adding the "-O3" flag. The -O3 flag enables levels 1, 2 and 3 of compile time optimization. There are more information about -O3 on gcc man page. For doing it, instead of previous line, use: $ CFLAGS="-O3  [blue string from above] " ./configure From:  http://blog.mybox.ro/2011/11/02...
Read more