From: "Jörn Engel" <joern@logfs.org>
To: Dongjun Shin <djshin90@gmail.com>
Cc: Greg Banks <gnb@sgi.com>,
Linux Filesystem Mailing List <linux-fsdevel@vger.kernel.org>,
David Chinner <dgc@melbourne.sgi.com>,
Donald Douwsma <donaldd@melbourne.sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Roger Strassburg <rls@sgi.com>, Mark Goodwin <markgw@sgi.com>,
Brett Jon Grandbois <brettg@melbourne.sgi.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Proposal to improve filesystem/block snapshot interaction
Date: Tue, 30 Oct 2007 15:06:25 +0100 [thread overview]
Message-ID: <20071030140624.GA13455@lazybastard.org> (raw)
In-Reply-To: <7fe698080710300235v3ce49613nfe3c5e733f1b6f5b@mail.gmail.com>
On Tue, 30 October 2007 18:35:08 +0900, Dongjun Shin wrote:
> On 10/30/07, Greg Banks <gnb@sgi.com> wrote:
> >
> > BIO_HINT_RELEASE
> > The bio's block extent is no longer in use by the filesystem
> > and will not be read in the future. Any storage used to back
> > the extent may be released without any threat to filesystem
> > or data integrity.
>
> I'd like to second the proposal, but it would be more useful to bring the hint
> down to the physical devices.
Absolutely. Logfs would love to have an erase operation for block
devices as well. However the above doesn't quite match my needs,
because the blocks _will_ be read in the future.
There are two reasons for reading things back later. The good one is to
determine whether the segment was erased or not. Reads should return
either valid data or one of (all-0xff, all-0x00, -ESOMETHING). Having
a dedicated error code would be best.
And getting the device erasesize would be useful as well, for obvious
reasons.
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-30 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070927063113.GD2989@sgi.com>
2007-10-30 1:04 ` Proposal to improve filesystem/block snapshot interaction Greg Banks
2007-10-30 1:11 ` Greg Banks
2007-10-30 4:16 ` Neil Brown
2007-10-30 5:12 ` Greg Banks
2007-10-30 7:43 ` Arnd Bergmann
2007-11-20 23:43 ` Roger Strassburg
2007-10-30 23:56 ` David Chinner
2007-10-31 4:01 ` Greg Banks
2007-10-31 7:04 ` David Chinner
2007-10-30 9:35 ` Dongjun Shin
2007-10-30 10:15 ` Arnd Bergmann
2007-10-30 10:49 ` Dongjun Shin
2007-10-30 12:38 ` Arnd Bergmann
2007-10-30 14:19 ` Dongjun Shin
2007-10-30 15:37 ` Jörn Engel
2007-10-30 16:37 ` Arnd Bergmann
2007-10-30 23:19 ` Kyungmin Park
2007-10-30 23:42 ` Kyungmin Park
2007-10-30 14:06 ` Jörn Engel [this message]
2007-10-31 3:44 ` Greg Banks
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=20071030140624.GA13455@lazybastard.org \
--to=joern@logfs.org \
--cc=arnd@arndb.de \
--cc=brettg@melbourne.sgi.com \
--cc=dgc@melbourne.sgi.com \
--cc=djshin90@gmail.com \
--cc=donaldd@melbourne.sgi.com \
--cc=gnb@sgi.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=markgw@sgi.com \
--cc=rls@sgi.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;
as well as URLs for NNTP newsgroup(s).