Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Jul 2017 15:55:56 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Manish Jain <bourne.identity@hotmail.com>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: Unable to mount USB Flash memory created on CentOS
Message-ID:  <20170729155556.00a1d838.freebsd@edvax.de>
In-Reply-To: <VI1PR02MB1200CF2B75A84A89EAF8B3CFF6BC0@VI1PR02MB1200.eurprd02.prod.outlook.com>
References:  <a491848b72ef4dc2282175cccf09e115.squirrel@webmail.harte-lyne.ca> <20170728223744.a94ce254.freebsd@edvax.de> <fc164e1b20c58429cb8f5dbb5ae876b5.squirrel@webmail.harte-lyne.ca> <20170729110144.1cce7c70.freebsd@edvax.de> <VI1PR02MB1200CF2B75A84A89EAF8B3CFF6BC0@VI1PR02MB1200.eurprd02.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Jul 2017 10:26:35 +0000, Manish Jain wrote:
> There is a significant problem with the ext2fs driver under FreeBSD. I 
> earlier thought this was perhaps a niggling issue, but this post 
> inclines me to mention it.
> 
> Create an ext2 partition and use it for a while. When there is an 
> improper shutdown/unclean umount, I experienced this syndrome 3 times in 
> the last 3 months : FreeBSD will refuse to mount the partition RW (which 
> is correct) - but then FreeBSD e2fsck will not be able to complete a 
> successful fsck. I think the error message from e2fsck used to be : 
> failed + run fsck. No further details. I don't remember what fsck used 
> to report, but nothing worked.

Yes, Linux file system support is limited, as UFS support is
limited on Linux, and nonexistent on non-UNIX... ;-)



> The only way to correct the situation always was - boot into Linux (I 
> use Parrot Lite), run e2fsck therein, and then mount it RW. Then get 
> back to FreeBSD, and now the partition gets mounted coolly.

That's why I suggested using the _native_ file system check and
repair tool is probably the best choice. FreeBSD's ext2 support
doesn't seem to be able to properly deal with those _specific_
cases of file system damage.

There is a port "e2fsprogs" which includes an e2fsck program.
I don't know if there's also a FUSE module for ext2 (and others)
that offers a comparable tool.



> If OP continues to suffer something similar, perhaps he can try fixing 
> things under Linux ?

That would be worth a try, even though I think in this special
case the file system _might_ be (partially?) intact, but at least
the partition table has suffered severe damage - it's not even
listing the ext2 partition correctly anymore. So maybe this can
be restored with a live system CD like PartEd Magic or UBCD...



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170729155556.00a1d838.freebsd>