*** 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
*** 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
*** 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
*** 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
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:
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
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
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
#
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
