From: Ivan Shapovalov <intelfx@intelfx.name>
To: Edward Shishkin <edward.shishkin@gmail.com>,
Reiserfs development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4: BUG during a backup (sequentially reading the whole fs) on 4.9
Date: Sat, 03 Jun 2017 02:21:30 +0300 [thread overview]
Message-ID: <1496445690.28911.1.camel@intelfx.name> (raw)
In-Reply-To: <5931CC9D.6080801@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Uh, I don't know exactly which partition is it. Strangely, I could not
reproduce this with a mock-up load (find -exec cat {} \; >/dev/null),
but odds are that it usually happens while reading a half-filled 500GB
partition.
Anyhow, I can put it on my public-facing NAS and give you either a
download link (my uplink is 50 Mbps wide) or ssh access, if you would
be kind enough to have a look at it :)
BTW, if I enable checkpoints in borg (so it saves internal state
periodically) and restart the backup from a checkpoint after the crash,
it always finishes successfully. Does that confirm or refute your
hypothesis?
Thanks,
--
Ivan Shapovalov / intelfx /
On 2017-06-02 at 23:37 +0300, Edward Shishkin wrote:
> Alas, can not reproduce it.
> I suspect garbage on the leaf level. For some reasons
> fsck can not detect it (on semantic pass).
> How big is your partition?
> Could you dd it to a file and let me download that file?
>
> Thanks,
> Edward.
>
> On 06/02/2017 01:59 AM, Ivan Shapovalov wrote:
> > Looking forward to your results.
> >
> > And by "looking at the tree" you mean the debugfs output, right?
> >
> > Thanks,
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-02 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 16:01 reiser4: BUG during a backup (sequentially reading the whole fs) on 4.9 Ivan Shapovalov
2017-02-27 16:17 ` Edward Shishkin
2017-02-27 16:20 ` Ivan Shapovalov
2017-02-27 16:30 ` Edward Shishkin
2017-06-01 14:49 ` Ivan Shapovalov
2017-06-01 17:43 ` Edward Shishkin
2017-06-01 17:46 ` Ivan Shapovalov
2017-06-01 20:00 ` Edward Shishkin
2017-06-01 22:59 ` Ivan Shapovalov
2017-06-02 20:37 ` Edward Shishkin
2017-06-02 23:21 ` Ivan Shapovalov [this message]
2017-06-03 7:39 ` Edward Shishkin
2017-06-05 13:41 ` Edward Shishkin
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=1496445690.28911.1.camel@intelfx.name \
--to=intelfx@intelfx.name \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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.