From: Dewet Diener <dewet@dewet.org>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Stephen C Tweedie <sct@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 partition unmountable
Date: Sun, 19 Aug 2001 01:40:21 +0200 [thread overview]
Message-ID: <20010819014021.B26332@darkwing.flatlit.net> (raw)
In-Reply-To: <20010818235211.A24646@darkwing.flatlit.net> <Pine.LNX.4.33.0108182257490.9206-100000@infradead.org>
In-Reply-To: <Pine.LNX.4.33.0108182257490.9206-100000@infradead.org>; from rhw@MemAlpha.CX on Sat, Aug 18, 2001 at 11:04:41PM +0100
On Sat, Aug 18, 2001 at 11:04:41PM +0100, Riley Williams wrote:
> The relevant mount option is to specify the ext3 rather than the ext2
> file system, and the flag you refer to gets set if ANYBODY sets the
> "COMPRESS THIS FILE" flag on ANY file on that file system. As far as I
> can tell, nothing ever resets that flag, even if the last file that
> was compressed gets uncompressed.
I doubt that ever happened - its pretty much a single-user system,
and I can't say that I quite know *how* to set that flag in the first
place :)
> You have an old version of tune2fs, and need to get the one that knows
> about ext3 or alternatively apply the patch that was distributed some
> time ago and recompile - I'm not sure which.
>
> Stephen: What's the current status regarding tune2fs and ext3, I'm a
> tad out of date in this respect?
I'm running e2fsprogs-1.22 (which is later than the one specified from
Documentation/Changes), so I kinda assumed everything was fine...
Dewet
next prev parent reply other threads:[~2001-08-18 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 1:03 ext3 partition unmountable Dewet Diener
2001-08-18 11:07 ` Mike Black
2001-08-18 21:52 ` Dewet Diener
2001-08-18 22:04 ` Riley Williams
2001-08-18 23:40 ` Dewet Diener [this message]
2001-08-20 18:10 ` Stephen C. Tweedie
2001-08-20 21:37 ` Dewet Diener
2001-08-18 22:29 ` Andrew Morton
2001-08-18 23:35 ` Dewet Diener
2001-08-19 14:06 ` Dewet Diener
2001-08-19 16:00 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010819014021.B26332@darkwing.flatlit.net \
--to=dewet@dewet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox