Bug #783
closedumount issue with NTFS filesystems
0%
Description
qbot# mount
/dev/ad0s4a on / (ufs, local)
procfs on /proc (procfs, local)
/dev/ad0s5 on /mnt/aparat (ntfs, local)
if I umount by path (/mnt/aparat) my box reboots
if I umount by device (/dev/ad0s5) it's ok
Updated by dillon over 17 years ago
:New submission from qermit <piotr.miedzik@etel.pl>:
:
:qbot# mount
:/dev/ad0s4a on / (ufs, local)
:procfs on /proc (procfs, local)
:/dev/ad0s5 on /mnt/aparat (ntfs, local)
:
:if I umount by path (/mnt/aparat) my box reboots
:if I umount by device (/dev/ad0s5) it's ok
Its really hard for me to test ntfs. Could you format a small ntfs
filesystem on, say, a usb memory stick, which reproduces the crashing
problem, and then dump an image of that filesystem and make it available
for download? I have no way of constructing a ntfs filesystem myself.
-Matt
Updated by floid over 17 years ago
Looks like there's a mkntfs is available in /usr/pkgsrc/sysutils/ntfsprogs
(Linux-NTFS.org tools), and I did the sanity-check of making sure it builds
before saying so.
-Cheers,
-Joe "Floid" Kanowitz
Updated by tuxillo over 15 years ago
Hi,
I can't reproduce this:
grep ntfs /etc/fstab
/dev/ad3s1 /mnt/ntfs ntfs ro 0 0
sudo mount /mnt/ntfs
mount -v | grep ntfs
/dev/ad3s1 on /mnt/ntfs (ntfs, local, read-only)
sudo umount /mnt/ntfs/
mount -v | grep ntfs
Can you please give us more details on how to reproduce it?
Cheers,
Antonio Huete
Updated by alexh almost 15 years ago
likely related to issue1671, which is fixed.