To read all comments associated with this story, please click here.
Very true. I was working on a TSM backup system that ran on SLES10SP1 PPC64 that used disk storage pool for catch (faster than tape). The backup disk catch pool was configured on 10 LUNs on a SAN which was mirrored to another SAN at a remote site for DRM purposes. All 10 LUNs where concatenated using LVM.
Problem was, the LUNs where mapped from 1 to 10 on the primary site, but from 7 to 17 on the secondary, DRM site so when you defined those LUNs as primary on the secondary site, then mounted them (again on exactly the same configuration, SLES10PPC), LVM would mix up the LUNs that where already mounted, i.e 1 to 6, with the newly mounted LUNs causing total data lose.
I understand that, in essence, the LUNs should have had the same mapped number on both system and that in retrospect, I should have known this, but had I done this with an AIX system, it would not have blinked an eye.
The only other time I have ever seen that sort of behaviour is with a HP-UX box. No wonder they call it HP-SUX! ;-)





Member since:
2007-06-01
...at the point where he said LVM is Linux Volume Management. LVM stands for Logical Volume Manager, and it was not invented with the birth of Linux. We use LVM all the time on various Unix boxes and god help us if we needed to use GUI. Linux LVM is a copy of the one HP-UX has, which is complete crap i have to admit that. Not to mention GRUB can't boot from LVM, which is like "WTF?!?!"