From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-raid@vger.kernel.org
Subject: Re: question about the best suited RAID level/layout
Date: Sun, 07 Jul 2013 19:39:21 +0200 [thread overview]
Message-ID: <1373218761.5246.11.camel@fermat.scientia.net> (raw)
In-Reply-To: <51D9631D.403@fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Sun, 2013-07-07 at 14:46 +0200, Bernd Schubert wrote:
> The block layer has no knowledge which file a block belongs to.
Sure...
> Even for
> file systems that is hard task to figure out, as only inodes store
> information which blocks they use. So if you would want to figure out
> the corresponding file, you first need to scan through all inodes and
> search for the specific block. Once you have the corresponding inode you
> need to find directory-entries referencing it. So lots of expensive
> reverse searching.
Well of course nothing that should run online in the RAID drivers... but
when you have a tool like raid6check or similar... it sounds nice if it
would tell you which files were affected (if any).
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5113 bytes --]
next prev parent reply other threads:[~2013-07-07 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:17 question about the best suited RAID level/layout Christoph Anton Mitterer
2013-07-04 21:43 ` Phil Turmel
2013-07-04 22:58 ` Christoph Anton Mitterer
2013-07-05 1:07 ` Brad Campbell
2013-07-06 0:36 ` Christoph Anton Mitterer
2013-07-06 5:29 ` Brad Campbell
2013-07-06 14:49 ` Christoph Anton Mitterer
2013-07-07 6:36 ` Brad Campbell
2013-07-06 7:40 ` Piergiorgio Sartor
2013-07-06 14:52 ` Christoph Anton Mitterer
2013-07-05 1:12 ` Stan Hoeppner
2013-07-06 0:46 ` Christoph Anton Mitterer
2013-07-06 8:36 ` Stan Hoeppner
2013-07-06 15:04 ` Christoph Anton Mitterer
2013-07-06 15:41 ` Matt Garman
2013-07-07 14:08 ` David Brown
2013-07-07 16:45 ` Stan Hoeppner
2013-07-07 17:26 ` Christoph Anton Mitterer
2013-07-09 15:50 ` Stan Hoeppner
2013-07-05 13:36 ` Phil Turmel
2013-07-06 1:11 ` Christoph Anton Mitterer
2013-07-06 2:19 ` Phil Turmel
2013-07-06 17:55 ` Christoph Anton Mitterer
2013-07-07 12:46 ` Bernd Schubert
2013-07-07 17:39 ` Christoph Anton Mitterer [this message]
2013-07-05 11:10 ` David Brown
2013-07-06 0:55 ` Christoph Anton Mitterer
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=1373218761.5246.11.camel@fermat.scientia.net \
--to=calestyo@scientia.net \
--cc=linux-raid@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 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).