Hi,
I have a UFS2 partition that I created with parted on Linux, and formatted on FreeBSD 10.0-RELEASE with
I did a fresh install of FreeBSD 10.1-RELEASE. I mount the partition as usual with
Upon booting into FreeBSD again, /dev/ada1s8 is marked as dirty. I can run
(I have backups, so I recreate the filesystem and restore the files at this point.)
The really strange thing is that if I (in FreeBSD) run
I can run
I expect downgrading to FreeBSD 10.0-RELEASE will solve the problem, but surely this is not supposed to happen so I thought it would be appropriate to start a thread about it.
I use FreeBSD 10.1-RELEASE i386 and the hard drive is a Western Digital SATA disk. I used the same disk with FreeBSD 10.0-RELEASE (when everything worked).
Any ideas?
I have a UFS2 partition that I created with parted on Linux, and formatted on FreeBSD 10.0-RELEASE with
newfs -O 2 -b 8192 -f 1024 /dev/ada1s8
. This partition is for sharing data between FreeBSD, OpenBSD and Linux (it's not inside the FreeBSD slice). It worked fine in FreeBSD 10.0-RELEASE (read-write), it works in OpenBSD 5.6 (read-write) and it works in Linux (read-only).I did a fresh install of FreeBSD 10.1-RELEASE. I mount the partition as usual with
mount -t ufs /dev/ada1s8 /dataufs
. This appears to work fine ( mount
does not indicate any error). But when I run ls /dataufs
, the ls command freezes forever, uses 100% CPU and can't be killed in any way.- ^C does not kill ls.
- ^Z to send ls to the background does not work. The whole TTY is frozen.
- Going to another TTY, logging in as root and running
kill -9
on the ls process does not kill the ls process. umount /dataufs
does not work, and the umount process freezes exactly like ls (the TTY becomes unusable and the process can't be killed in any way).
shutdown -r now
. This sometimes reboots the system (after a long wait, presumably it waits for ls and umount to die), but sometimes the whole system freezes and does not reboot no matter how long I wait, requiring a hard reboot.Upon booting into FreeBSD again, /dev/ada1s8 is marked as dirty. I can run
fsck -y
on it, which corrects approximately a few dozen to hundred errors about block sizes. Attempting to mount it again results in the same freeze.(I have backups, so I recreate the filesystem and restore the files at this point.)
The really strange thing is that if I (in FreeBSD) run
newfs -O 2 -b 8192 -f 1024 /dev/ada1s8
then the partition works, can be mounted, ls
works, and I can use it normally. However when I reboot FreeBSD and attempt to use the partition, then the freeze happens again (I can reproduce it every time without exception and I have gone through this 5-10 times now). When I recreate the filesystem with newfs, then I can use it again until I reboot.I can run
dumpfs
on the partition (in FreeBSD) and everything looks sane. I can also mount the partition on Linux (read-only because the kernel doesn't support UFS2 read-write) and access all files without any problems, and the partition works fine in OpenBSD (read-write). smartctl
says the disk is in perfect condition and the self-tests return no errors (as expected because the disk is new).I expect downgrading to FreeBSD 10.0-RELEASE will solve the problem, but surely this is not supposed to happen so I thought it would be appropriate to start a thread about it.
I use FreeBSD 10.1-RELEASE i386 and the hard drive is a Western Digital SATA disk. I used the same disk with FreeBSD 10.0-RELEASE (when everything worked).
Any ideas?