[Bug 153600] Re: xfs /home cannot be mounted on boot
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 I found out I was wrong: maybe I have too many computers... I did remove EVMS, but from the wrong computer :-P I *confirm* that you cannot mount some additional partitions (I'd say regardless of which filesystem they use, not only XFS) if you have evms installed and active. So, to be able to mount those partition again by device or by UUID or label, you can simply remove EVMS (that is, simply if you don't use it). If you can't, use the /dev/mapper/ devices managed by EVMS. This has to do with bug #115616 (that explain that new device locking policies blocks concurrent access to a device from EVMS and other processes) but I think in this bug this relation wasn't explained very well. I hope this clarification will be helpful for someone, sorry for the mistake! Ciao, RobM -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 This bug is *NOT* a duplicate of bug #115616 The fact that the reporter sees evms errors in /var/log/messages does NOT mean he can mount XFS volumes by removing it. I confirm that: - I don't have EVMS installed - I can not mount any xfs volume either by old device (dev/sdax) or UUID. I only get the already mounted or busy error - I can mount the partitions using /dev/mapper/sdax So basically, I'd say we're without standard XFS support with gutsy -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 4YI I got the mounting working by using: mount -t xfs /dev/mapper/1ATA-*snip*p1 /mnt HAND -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 apt-get remove evms ** This bug has been marked a duplicate of bug 115616 Device-mapper errors: dm-linear, lookup failed -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
I can see those errors in kern.log too: Oct 17 15:25:18 tuxia kernel: [ 32.064000] EXT3 FS on hda1, internal journal Oct 17 15:25:18 tuxia kernel: [ 33.036000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.036000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.04] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.04] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.04] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.04] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.044000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.044000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.044000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.048000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.288000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.288000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.368000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.368000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.376000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.376000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.38] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.38] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.38] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.38] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.384000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.384000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.384000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.384000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.388000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.388000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.388000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.388000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.392000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.392000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.392000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.392000] device-mapper: ioctl: error adding target to table Oct 17 15:25:18 tuxia kernel: [ 33.396000] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed Oct 17 15:25:18 tuxia kernel: [ 33.396000] device-mapper: ioctl: error adding target to table Kernel version is 2.6.22-14-386. When I choose the old Feisty's kernel in GRUB menu (kernel version 2.6.20-16-386), /home mount fine and there are no device mapper errors: Oct 19 11:59:59 tuxia kernel: [ 30.236000] EXT3 FS on hda1, internal journal Oct 19 11:59:59 tuxia kernel: [ 32.268000] eth0: no IPv6 routers present Oct 19 11:59:59 tuxia kernel: [ 47.736000] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled Oct 19 11:59:59 tuxia kernel: [ 47.736000] SGI XFS Quota Management subsystem Oct 19 11:59:59 tuxia kernel: [ 47.804000] XFS mounting filesystem hda6 Oct 19 11:59:59 tuxia kernel: [ 47.892000] Ending clean XFS mount for filesystem: hda6 -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
I have /home on a clean ext3 partition with the same problem (changed /etc/apt/source.list to Gutsy, did a dist-upgrade and now /home does not mount). I can delete /home so it does not seem to be locked at that level. I can create a new partition, but cannot mount /dev/sda4 there either: it gives the same error * sudo mkdir /newhome * sudo mount -t ext3 /dev/sda4 /newhome * mount: /dev/sda4 already mounted or /newhome busy -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
I'm experiencing the same thing. / on sda1, /home (ext3) on sda7 (which resides on the extended partition sda2) My fstab is in order, I've tried using both UUID and device. The only thing I can find in /var/log that relates to this is (probably): [ 43.436407] Adding 4554388k swap on /dev/sda5. Priority:-1 extents:1 across:4554388k [ 43.725791] EXT3 FS on sda1, internal journal [ 44.402622] device-mapper: table: 254:3: linear: dm-linear: Device lookup failed [ 44.402631] device-mapper: ioctl: error adding target to table (the last two rows repeats ~20 times) -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
Actually I was wrong with the usage - I was testing whether /home is in use with fuser -m /home. I've added the -m argument out of habit. Actually, /home seems to be unused - plain fuser /home shows no accessing processes. So the cause seems to be different. The symptoms are: # fuser /home # mount /dev/hda6 /home/ mount: /dev/hda6 already mounted or /home/ busy # mount -v -t xfs /dev/hda6 /home/ mount: /dev/hda6 already mounted or /home/ busy # hexdump -C /dev/hda6 | head 58 46 53 42 00 00 10 00 00 00 00 00 01 96 52 e0 |XFSB..R.| 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || 0020 c9 e3 cb ee 47 e0 11 d7 9f 33 ed 99 1e fa c2 d0 |G3..| 0030 00 00 00 00 00 d0 00 04 00 00 00 00 00 00 00 80 || 0040 00 00 00 00 00 00 00 81 00 00 00 00 00 00 00 82 || 0050 00 00 00 10 00 10 00 00 00 00 00 1a 00 00 00 00 || 0060 00 00 0c b2 20 94 02 00 01 00 00 10 00 00 00 00 | ...| 0070 00 00 00 00 00 00 00 00 0c 09 08 04 14 00 00 19 || 0080 00 00 00 00 00 05 c7 80 00 00 00 00 00 01 de a2 || 0090 00 00 00 00 00 32 0f 26 00 00 00 00 00 00 00 00 |.2.| A sidenote to Stephen: On POSIX systems (including Linux) you actually _can_ delete files and directories that are in use, since they are identified by their inode numbers. So if your /home directory is used by some processes, you can still rmdir or rm -rf it and it will disappear. You can mkdir a new /home, and it will be a different one, and the processess holding the old one will still see the old one. Its space will be reclaimed in the filesystem when the last process to use it will close its handle. You can test a filesystem object's usage using the fuser command. But to be used as a mount point, a directory cannot be in use. -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153600] Re: xfs /home cannot be mounted on boot
I get this error if I use kernel 2.6.22-14-generic and -386. The problem goes away if I reboot with 2.6.20-16-generic and -386 from Feisty, or 2.6.20-16-realtime. -- xfs /home cannot be mounted on boot https://bugs.launchpad.net/bugs/153600 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
