man mount, section BUGS:
It is possible that files /etc/mtab and /proc/mounts don’t match. The
first file is
based only on the mount command options, but the content of the
second file also
depends on the kernel and others settings (e.g. remote NFS server. In
Note that the problem with fuse sshfs should be fixed by util-linux-2.19
(for more detail see the fstab.5 man page and a note about subtype).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/99437
Fixed in upstream repository -- commit
973d9cf9c6092d94a3e5b54e5b8e7cd4e2d705d7.
--
umount segfault on shutdown when unmounting autofs mountpoint
https://bugs.launchpad.net/bugs/579858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm not sure if there is any direct relation... but there is a bug in
libblkid, the blkid command believes that whole iPod disk (e.g.
/dev/sdd) is unpartitioned device with FAT filesystem. Try:
blkid -p -o udev -p /dev/sdd
The incorrect output is
ID_FS_LABEL=iPod
ID_FS_LABEL_ENC=iPod
Fixed by upstream commit 6c7f688b1f46c6fb31aa8a4a27d493c90e9ded37.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726283
Title:
umount segfaults with inconsistent entry in /etc/fstab
--
Upstream patch (fixed 14 days ago...)
http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=commit;h=74b1659ddaac4aa409b56d1eaa07d87b5b11b98e
The patch is also included in the bugfix release 2.17.2.
--
mount ext fileystem fails, booting fails, blkid produces no output
50mounted-tests just calls blkid -o value -s TYPE /dev/sda2
Note that since util-linux-ng 2.17 you can use low-probe mode (to avoid
/etc/blkid.tab cache) for this task, it means:
blkid -p -o value -s TYPE device
Thanks for the patch.
--
blkid (sometimes?) hangs on extended partition if
The mount(8) from upstream git tree uses MS_SILENT so the warnings
should not be visible any more. If you want to use whitelist then use
/etc/filesystems ... see man page. Note that the current upstream stable
release is 2.23.
--
You received this bug notification because you are a member of
Kernel patch http://www.spinics.net/lists/linux-fsdevel/msg89010.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277146
Title:
mount -o loop changes the udf image
To manage notifications
The command mount(8) does not write anywhere, if you see any change in
the filesystem then it's done by kernel filesystem driver.
I guess the confusing thing for users is that mount(8) command calls
mount(2) syscall two times:
# strace -e mount mount /dev/loop0 /mnt/test
mount(/dev/loop0,
Fixed in upstream tree. Thanks for your report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800167
Title:
fstrim: /var/spool/postfix/etc/sasldb2: not a directory
To manage notifications about
11 matches
Mail list logo