As fsck tail on it# fsck -n ad0s3f was fsck_4.2bsd: bad inode number 376832 to nextinode I tried do see what was there. On doing it# fsdb /dev/ad0s3f ** /dev/ad0s3f Editing file system `/dev/ad0s3f' Last Mounted on /mnt current inode: directory I=2 MODE=40755 SIZE=512 MTIME=Dec 6 21:13:52 2003 [0 nsec] CTIME=Dec 6 21:13:52 2003 [0 nsec] ATIME=Dec 6 20:53:14 2003 [0 nsec] OWNER=root GRP=wheel LINKCNT=24 FLAGS=0 BLKCNT=4 GEN=3e836771 fsdb (inum: 2)> inode 376832 current inode: regular file I=376832 MODE=104116 SIZE=2702796530890628197 MTIME=Sep 18 02:17:44 1939 [-355479186 nsec] CTIME=May 16 13:00:35 1948 [632285737 nsec] ATIME=Oct 12 14:25:49 1953 [669062497 nsec] OWNUID=3946099571 GID=3224811878 LINKCNT=31343 FLAGS=0xb8cb0034 BLKCNT=b5cd63e58ad40580 GEN=ffffffff8275e84d if I do here a blocks the system panics with: panic: Negative bio_offset (-7150880186449909760) on bio 0xce58bfe8 I have a dump but no kernel.debug , so im compiling now a debug kernel. -- IOnut Unregistered ;) FreeBSD userReceived on Mon Dec 08 2003 - 09:14:48 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:32 UTC