Date: Mon, 06 Jan 2003 00:14:15 +0100 From: phk@freebsd.org To: Rahul Siddharthan <rsidd@online.fr> Cc: freebsd-current@freebsd.org Subject: Re: Unable to mount ext2fs partition Message-ID: <12670.1041808455@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 05 Jan 2003 18:11:44 EST." <20030105231144.GA77444@papagena.rockefeller.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030105231144.GA77444@papagena.rockefeller.edu>, Rahul Siddharthan writes: >phk@freebsd.org wrote: >> ># e2fsck -n /dev/ad0s2 >> >e2fsck 1.27 (8-Mar-2002) >> >The filesystem size (according to the superblock) is 714892 blocks >> >The physical size of the device is 0 blocks >> >Either the superblock or the partition table is likely to be corrupt! >> >Abort? no >> > >> >/dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks >> > >> >So what does that mean? Any way to fix it? >> >> Can you send us the output of >> sysctl -b kern.geom.conftxt >> please ? > >0 DISK ad0 10056130560 512 hd 16 sc 63 >1 MBR ad0s2 2928199680 512 i 1 o 7123092480 ty 131 >1 MBR ad0s1 7123060224 512 i 0 o 32256 ty 165 >2 BSD ad0s1e 6816876032 512 i 4 o 306184192 >2 BSD ad0s1c 7123060224 512 i 2 o 0 >2 BSD ad0s1b 201326592 512 i 1 o 104857600 >2 BSD ad0s1a 104857600 512 i 0 o 0 Hmm, I can't see anything wrong here. I'm not an EXT2 specialist, and I don't really intend to become one, so I hope somebody else can help you out... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12670.1041808455>