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: Fri, 02 Jun 2017 01:59:07 +0300 [thread overview]
Message-ID: <1496357947.4940.2.camel@intelfx.name> (raw)
In-Reply-To: <59307242.5010705@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Looking forward to your results.
And by "looking at the tree" you mean the debugfs output, right?
Thanks,
--
Ivan Shapovalov / intelfx /
On 2017-06-01 at 23:00 +0300, Edward Shishkin wrote:
> I'll try to reproduce it on my side tomorrow, or on weekends.
> If no success, then we'll think what to do. Specifically, I'd like
> to look at the tree in the locality of the current search position,
> where the oops happens.
>
> Thanks,
> Edward.
>
> On 06/01/2017 08:46 PM, Ivan Shapovalov wrote:
> > Yes, it is reproducible each time when I backup to an empty repo
> > without checkpoints (so that borg has to fully read all files). The
> > filesystem is consistent by fsck.
> >
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-01 22:59 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 [this message]
2017-06-02 20:37 ` Edward Shishkin
2017-06-02 23:21 ` Ivan Shapovalov
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=1496357947.4940.2.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 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).