Date: Sun, 5 Jan 2003 18:22:19 -0500 From: Rahul Siddharthan <rsidd@online.fr> To: phk@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Unable to mount ext2fs partition Message-ID: <20030105232219.GA93064@papagena.rockefeller.edu> In-Reply-To: <12670.1041808455@critter.freebsd.dk> References: <20030105231144.GA77444@papagena.rockefeller.edu> <12670.1041808455@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
phk@freebsd.org said on Jan 6, 2003 at 00:14:15: > I'm not an EXT2 specialist, and I don't really intend to become one, > so I hope somebody else can help you out... As posted earlier, there seems to be "funny stuff" on my ufs disklabel too: # disklabel -r /dev/ad0s1 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 204800 63 4.2BSD 0 0 0 # (Cyl. 0*- 12*) b: 393216 204863 swap # (Cyl. 12*- 37*) c: 13912227 63 unused 0 0 # (Cyl. 0*- 865*) e: 13314211 598079 4.2BSD 0 0 0 # (Cyl. 37*- 865*) Warning, partition c doesn't start at 0! Warning, partition c doesn't cover the whole unit! Warning, An incorrect partition c may cause problems for standard system utilities Should I worry about that? As for the ext2fs partition: I can probably live with it. But it may bite more people after the -RELEASE.... Not sure whether this information is relevant, but the ext2 partition was originally a UFS partition. A few months ago I changed it to ext2 with freebsd 4.x's fdisk and then newfs'd with the linux mke2fs binary under linux emulation (FreeBSD 4.x, again). I then wrote a gentoo bootstrap filesystem to it and was able to boot it via grub. It's worked fine since then (I haven't messed with it again under freebsd, and it's mostly been mounted read-only). - Rahul 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?20030105232219.GA93064>