From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Add flag to files with blocks intentionally past EOF
Date: Fri, 22 Jan 2010 11:40:56 -0600 [thread overview]
Message-ID: <4B59E328.8020008@redhat.com> (raw)
In-Reply-To: <22655F73-6EB0-40AC-9D51-794F6764CF67@sun.com>
Andreas Dilger wrote:
> On 2010-01-20, at 02:03, Aneesh Kumar K. V wrote:
...
>> If we remove ext4_ioctl support i guess that patch can become much
>> simpler.
>
>
> Sure it will be simpler, but less useful. The point of exposing this
> flag via lsattr is to allow userspace to determine which files are
> holding blocks beyond EOF, so that if the filesystem is getting too full
> it is possible to run e.g. "lsattr -R" and find files with this EOF
> attribute and truncate them. Without keeping at least the EOFBLOCKS
> flag in USER_VISIBLE this is impossible.
Well, I submitted an updated patch without it. We can add another when
we sort out what we really want with the flags, but fixing the
corruption e2fsck finds seems paramount.
I think the case of stray files w/ blocks past EOF is probably pretty
rare - but I guess I agree, at least seeing the flags would be nice.
But let's handle that separately...
-Eric
next prev parent reply other threads:[~2010-01-22 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 21:45 [PATCH] Add flag to files with blocks intentionally past EOF Eric Sandeen
2010-01-20 0:46 ` Mingming
2010-01-20 3:58 ` Eric Sandeen
2010-01-20 8:37 ` Andreas Dilger
2010-01-20 9:15 ` Aneesh Kumar K. V
2010-01-20 9:03 ` Aneesh Kumar K. V
2010-01-22 0:32 ` Andreas Dilger
2010-01-22 17:40 ` Eric Sandeen [this message]
2010-01-21 18:00 ` [PATCH V2] " Eric Sandeen
2010-01-21 20:32 ` Jiaying Zhang
2010-02-24 16:26 ` tytso
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=4B59E328.8020008@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.