Date: Sun, 20 Nov 2005 13:02:33 +0100 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= <v.haisman@sh.cvut.cz> To: freebsd-stable@freebsd.org Subject: Mount related panic with FreeBSD 6? Message-ID: <dlpolp$9t$1@sea.gmane.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCDE950563F86E1AD60F45A34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, I got this panic on freshly installed FreeBSD 6. I did this df -h and noticed that /mnt/oldroot/home is somewhat mangled. The /mnt/oldroot is root of FreeBSD 4.11 system. I successfully copied some settings and all user accounts from that /mnt/oldroot/home earlier today. This is what I did before the panic: logout::wilx:~> df -h Filesystem Size Used Avail Use% Mounted on /dev/ad0s1a 496M 57M 399M 13% / devfs 1.0k 1.0k 0 100% /dev /dev/ad0s1e 989M 12k 910M 1% /tmp /dev/ad0s1f 163G 29G 120G 20% /usr /dev/ad0s1d 4.8G 2.0G 2.4G 45% /var /dev/ad2s1a 492M 317M 136M 70% /mnt/oldroot df: `/mnt/oldroot/hom': No such file or directory /dev/ad2s1f 6.7G 5.3G 1013M 85% /mnt/oldroot/usr /dev/ad2s1e 2.9G 2.2G 476M 83% /mnt/oldroot/var logout::root:~> mount /mnt/oldroot/home Notice that /mnt/oldroot/home is mounted twice here: logout::root:~> mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) /dev/ad2s1a on /mnt/oldroot (ufs, local, read-only) /dev/ad2s1g on /mnt/oldroot/home (ufs, local, read-only) /dev/ad2s1f on /mnt/oldroot/usr (ufs, local, read-only) /dev/ad2s1e on /mnt/oldroot/var (ufs, local, read-only) /dev/ad2s1g on /mnt/oldroot/home (ufs, local, read-only) logout::root:~> umount /mnt/oldroot/home logout::root:~> mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) /dev/ad2s1a on /mnt/oldroot (ufs, local, read-only) /dev/ad2s1g on /mnt/oldroot/home (ufs, local, read-only) /dev/ad2s1f on /mnt/oldroot/usr (ufs, local, read-only) /dev/ad2s1e on /mnt/oldroot/var (ufs, local, read-only) logout::root:~> cd /mnt/oldroot/home logout::root:/mnt/oldroot/home> ls After the ls it panicked. The only thing I see in logs is this: Nov 20 12:42:02 logout savecore: reboot after panic: page fault Nov 20 12:42:02 logout savecore: writing core to vmcore.0 Unfortunatelly trying gdb on the core didn't help. The kernel is still the generic one from the release CD: warning: "/var/crash/vmcore.0": no core file handler recognizes format, using default Can't fetch registers from this type of core file Can't fetch registers from this type of core file #0 0x00000000 in ?? () I realise that this might have been already fixed after the release. I will try to cvsup the sources and build a new kernel. Vaclav Haisman --------------enigCDE950563F86E1AD60F45A34 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQEVAwUBQ4Bl5G56zbtzMDG0AQJctwf+Jm9+tk7givXXKDNN83vMY0j99uPajCBQ Dy5FDL3eYjrhx8tvdd2TnzVsZJlQMCdY9dIxKYimUfOLs+1lE7HlimwXXRS5DCz7 s/yDMXDu99MuexPVMPaTPA0SU8Pqd0Ac/XTc/QMaMJlY1mSJDcseYpth2GaFKvoY Zm5BdgePjqH8Y9v3ZJNV6domb6qH0kETyc8CXgzngbj5DlvdqJBa2PId/4Egv4y4 IoivdxhICUXazVVyjPBC0ltu6szMh9CJ7D7pVlUeJwwD/tBnA5huZAwIS4gJNIbF RoMHc2qbtnqjDBsBj8rKWHs1kDsVGMn7nv9ld1IhmTZlsRfwy9KGLQ== =2BO7 -----END PGP SIGNATURE----- --------------enigCDE950563F86E1AD60F45A34--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dlpolp$9t$1>