search for: misassign

...does not use any locks. From here [1]: "The out of the box configuration, however, currently uses the nop lock manager plugin". As "lock_manager" is commented in my qemu.conf file, I was expecting that no locks were used to protect my virtual disk from guest double-start or misassignement to other vms. However, "cat /proc/locks" shows the following (17532905 being the vdisk inode): [root@localhost tmp]# cat /proc/locks | grep 17532905 42: OFDLCK ADVISORY READ -1 fd:00:17532905 201 201 43: OFDLCK ADVISORY READ -1 fd:00:17532905 100 101 Indeed, try to associate an...

...dev/md1 is a RAID1 consisting of /dev/sda2 and /dev/sdb2 /dev/md2 (our special friend) is a RAID5 consisting of /dev/sd[c-j] /dev/sdi and /dev/sdj were the drives that detached from the array and were marked as faulty. I did the following things that in hindsight were probably VERY BAD Step 1 (Misassign drives to wrong array): I could probably have had things going again in a tenth of a second if I hadn't typed this: mdadm --manage --add /dev/md0 /dev/sdi mdadm --manage --add /dev/md0 /dev/sdi This clobbered the superblock and replaced it with that of /dev/md0, yes? well, that's what...

...e: > fred smith wrote: > > > > Thanks for the additional information. > > > > I'll try backing up everything this weekend then will take a stab at it. > > > > someone said earlier that the differing raid superblocks were probably > > the cause of the misassignment in the first place. but I have no clue > > how the superblocks could have become messed up, can any of you comment > > on that? willl I need to hack at that issue, too, before I can succeed? > > > > thanks again! > > > > > >> Nataraj > >>...

...y locks. > From here [1]: "The out of the box configuration, however, currently > uses the nop lock manager plugin". As "lock_manager" is commented in > my qemu.conf file, I was expecting that no locks were used to protect > my virtual disk from guest double-start or misassignement to other > vms. > > However, "cat /proc/locks" shows the following (17532905 being the > vdisk inode): > [root@localhost tmp]# cat /proc/locks | grep 17532905 > 42: OFDLCK ADVISORY READ -1 fd:00:17532905 201 201 > 43: OFDLCK ADVISORY READ -1 fd:00:17532905...

Filed a ticket for bogus Ruby produced via: rake db_schema_dump http://dev.rubyonrails.org/ticket/3232 I''d appreciate it if someone could verify against PostgreSQL 8.0.x -- -- Tom Mornini

...rom here [1]: "The out of the box configuration, however, currently > > uses the nop lock manager plugin". As "lock_manager" is commented in > > my qemu.conf file, I was expecting that no locks were used to protect > > my virtual disk from guest double-start or misassignement to other > > vms. > > > > However, "cat /proc/locks" shows the following (17532905 being the vdisk > > inode): > > [root@localhost tmp]# cat /proc/locks | grep 17532905 > > 42: OFDLCK ADVISORY READ -1 fd:00:17532905 201 201 > > 43: OFDLCK...