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: Thu, 3 Jan 2013 22:49:13 +0100 [thread overview]
Message-ID: <20130103214913.GE2080@wloczykij> (raw)
In-Reply-To: <1356415552.2052.11.camel@slavad-ubuntu>
[-- Attachment #1: Type: text/plain, Size: 4395 bytes --]
On Tue, Dec 25, 2012 at 10:05:52AM +0400, Vyacheslav Dubeyko wrote:
> Hi Piotr,
>
> On Fri, 2012-11-30 at 08:32 +0100, Piotr Szymaniak wrote:
> > On Fri, Nov 30, 2012 at 10:09:04AM +0400, Vyacheslav Dubeyko wrote:
> > > Hi,
> > >
> > > On Thu, 2012-11-29 at 22:06 +0100, Piotr Szymaniak wrote:
> > > > Hello.
> > > >
> > > > Doing some work today (system update, kernel update, rsync rootfs with
> > > > external drive) I noticed some unwanted behaviour:
> > > > maszn ~ # touch afile
> > > > touch: cannot touch ‘afile’: System plików wyłącznie do odczytu
> > > > it's Read only filesystem
> > > >
> > > > dmesg shows a lot (1812 in the log) of:
> > > > [ 8288.319012] NILFS: bad btree node (blocknr=26229286): level = 178,
> > > > flags = 0x0, nchildren = 0
> > > > [ 8288.319017] NILFS error (device sda2): nilfs_bmap_lookup_contig:
> > > > broken bmap (inode number=102230)
> > > >
> > > > After mount -o remount,rw /
> > > > [ 8384.734024] segctord starting. Construction interval = 300 seconds,
> > > > CP frequency < 30 seconds
> > > > [ 8384.734028] NILFS warning: mounting fs with errors
> > > >
> > > > Never happend before and it looks like it works fine now (using vanilla
> > > > kernel 3.6.4).
> > > >
> > > > After a reboot (to vanilla kernel 3.6.8) dmesg shows:
> > > > [ 6.046883] segctord starting. Construction interval = 300 seconds,
> > > > CP frequency < 30 seconds
> > > > [ 6.046884] NILFS warning: mounting fs with errors
> > > >
> > > > I don't like the "errors" part...
> > > >
>
> Did you have any snapshots on this volume or not?
No, only checkpoints (just checked).
Also, got this issue again. A *lot* of:
Jan 03 22:36:38 [kernel] [ 953.289973] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:36:38 [kernel] [ 953.289976] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
Jan 03 22:36:38 [kernel] [ 953.289976]
Jan 03 22:36:38 [kernel] [ 953.290248] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:36:38 [kernel] [ 953.290251] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
Jan 03 22:36:38 [kernel] [ 953.290251]
Jan 03 22:36:38 [kernel] [ 953.290523] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:36:38 [kernel] [ 953.290526] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
Then I remounted rw and tried again (i was rsyncing my whole rootfs to
another drive):
Jan 03 22:38:15 [kernel] [ 1050.290134] segctord starting. Construction
interval = 300 seconds, CP frequency < 30 seconds
Jan 03 22:38:15 [kernel] [ 1050.290135] NILFS warning: mounting fs with
errors
Jan 03 22:38:15 [nilfs_cleanerd] start
Jan 03 22:38:15 [nilfs_cleanerd] pause (clean check)
Jan 03 22:38:40 [kernel] [ 1075.157346] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:38:40 [kernel] [ 1075.157351] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
Jan 03 22:38:40 [kernel] [ 1075.157351]
Jan 03 22:38:40 [kernel] [ 1075.157352] Remounting filesystem read-only
Jan 03 22:38:40 [kernel] [ 1075.159162] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:38:40 [kernel] [ 1075.159168] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
Jan 03 22:38:40 [kernel] [ 1075.159168]
Jan 03 22:38:40 [kernel] [ 1075.161003] NILFS: bad btree node
(blocknr=26229286): level = 67, flags = 0xee, nchildren = 40
Jan 03 22:38:40 [kernel] [ 1075.161019] NILFS error (device sda2):
nilfs_bmap_lookup_contig: broken bmap (inode number=102230)
But, thanks to rsync I got a (corupted?) file that causes the problem.
It's some /var/tmp/kdecache-$USER/foo.kcache. copying this file to
another place ends with readonly.
Piotr Szymaniak.
--
- Chyba nie jest pan jednym z tych roniacych lzy liberalow?
- Odmawiam odpowiedzi, poniewaz moglaby zostac wykorzystana przeciwko
mnie - odparlem. Taksiarz wydal prychniecie oznaczajace dlaczego-ja-
zawsze-trafiam-na-takich-cwaniakow... ale zamknal sie.
-- Stephen King, "The Breathing Method"
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-03 21:49 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 [this message]
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
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=20130103214913.GE2080@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 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.