From: Sergey Vlasov <vsu@altlinux.ru>
To: Doug Ledford <dledford@redhat.com>
Cc: Gabor Gombas <gombasg@sztaki.hu>,
Erik Mouw <erik@harddisk-recovery.com>,
linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: avoiding the initial resync on --create
Date: Tue, 10 Oct 2006 23:18:28 +0400 [thread overview]
Message-ID: <20061010231828.72d68502.vsu@altlinux.ru> (raw)
In-Reply-To: <1160502476.2917.134.camel@fc6.xsintricity.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Tue, 10 Oct 2006 13:47:56 -0400 Doug Ledford wrote:
[...]
> So, like my original email said, fsck has no business reading any block
> that hasn't been written to either by the install or since the install
> when the filesystem was filled up more. It certainly does *not* read
> blocks just for the fun of it, nor does it rely on anything the
> filesystem didn't specifically write.
There are fsck implementations which read potentially unwritten
blocks. E.g., reiserfsck --rebuild-tree reads every block on the
device, finds anything which looks like a tree block and tries to
do something with it. This procedure sometimes recovers files
which were deleted, and if an uncompressed image of a reiserfs v3
filesystem was stored in a file on reiserfs, it can confuse
reiserfsck badly...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-10 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 12:57 avoiding the initial resync on --create martin f krafft
2006-10-09 13:49 ` Erik Mouw
2006-10-09 16:32 ` Doug Ledford
2006-10-09 19:10 ` Rob Bray
2006-10-09 19:45 ` Doug Ledford
2006-10-09 21:33 ` Neil Brown
2006-10-09 21:45 ` Doug Ledford
2006-10-09 23:14 ` Neil Brown
2006-10-11 21:24 ` Michael Tokarev
2006-10-10 9:55 ` Gabor Gombas
2006-10-10 17:47 ` Doug Ledford
2006-10-10 19:18 ` Sergey Vlasov [this message]
2006-10-10 20:38 ` Doug Ledford
2006-10-10 20:37 ` Gabor Gombas
2006-10-10 21:26 ` Doug Ledford
2006-10-10 22:14 ` Rev. Jeffrey Paul
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=20061010231828.72d68502.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=dledford@redhat.com \
--cc=erik@harddisk-recovery.com \
--cc=gombasg@sztaki.hu \
--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).