From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: A lot of NILFS: bad btree node messages (readonly fs)
Date: Sat, 5 Jan 2013 17:47:52 +0100 [thread overview]
Message-ID: <20130105164752.GG2080@wloczykij> (raw)
In-Reply-To: <C2F4A5DE-538B-4468-9A6A-BA619EDDA462-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Sat, Jan 05, 2013 at 02:40:19PM +0300, Vyacheslav Dubeyko wrote:
> I simply try to collect enough details about the issue for deep
> understanding of it. There are two ways of issue investigation: (1)
> reproducing on my side; (2) preparing special debug output that can
> give more details about the issue on your side. So, I feel necessity
> to prepare a patch with additional debug output that can be enabled in
> NILFS2 in the case of special needs.
>
> Currently, I have such understanding of the situation. As I can see
> from the error output and preliminary code analysis, it occurs
> situation when allocation code discovers that memory page is uptodate
> before reading. It can means that we have synchronization issue. But
> it needs to investigate situation more deeply.
>
> Now I am preparing patch for another issue with very long mount time.
> So, when I end this activity then I begin more deep investigation of
> the issue with readonly fs.
Ok, I'll wait. Good thing it's just some KDE cache file. (:
Piotr Szymaniak.
--
Czujesz ostatni oddech opuszczajacy ich ciala. Patrzysz w ich oczy.
Osoba w takiej sytuacji jest Bogiem!
-- Theodore Robert Bundy
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-05 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 21:06 A lot of NILFS: bad btree node messages (readonly fs) Piotr Szymaniak
2012-11-30 6:09 ` Vyacheslav Dubeyko
2012-11-30 7:32 ` Piotr Szymaniak
2012-12-25 6:05 ` Vyacheslav Dubeyko
2012-12-25 20:54 ` Piotr Szymaniak
2013-01-03 21:49 ` Piotr Szymaniak
2013-01-04 12:46 ` Vyacheslav Dubeyko
[not found] ` <28ABE57F-66DD-491E-9FDB-A6CE3CF773FB-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-04 19:16 ` Piotr Szymaniak
2013-01-05 11:40 ` Vyacheslav Dubeyko
[not found] ` <C2F4A5DE-538B-4468-9A6A-BA619EDDA462-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-05 16:47 ` Piotr Szymaniak [this message]
2013-01-08 12:52 ` Vyacheslav Dubeyko
[not found] ` <504C0292-D0C6-426C-BDFD-1CD50FB32617-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-09 6:20 ` Elmer Zhang
[not found] ` <30D452FB-F1A5-425C-97ED-1A12CA4DCFD9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-09 12:10 ` Vyacheslav Dubeyko
2013-01-09 21:09 ` Piotr Szymaniak
2013-01-10 7:12 ` Vyacheslav Dubeyko
2013-01-12 21:24 ` Piotr Szymaniak
2013-01-14 19:32 ` Vyacheslav Dubeyko
2012-11-30 7:46 ` ARAI Shun-ichi
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=20130105164752.GG2080@wloczykij \
--to=szarpaj-tbom9ca2r9grdjvtcaxf/a@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.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