All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: A lot of NILFS: bad btree node messages (readonly fs)
Date: Thu, 29 Nov 2012 22:06:51 +0100	[thread overview]
Message-ID: <20121129210650.GA4028@wloczykij> (raw)

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

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...


Piotr Szymaniak.
-- 
 - Nie doceniasz sie - zaoponowal. - Jestes samoukiem,  madrym facetem.
W dodatku, moim zdaniem, dosc niezwyklym.
 - Hej, nawet nie mam matury.
 - Wiem - odparl. - Jednak to nie kawalek papieru stanowi o czlowieku.
  -- Stephen King, "Rita Hayworth and Shawshank Redemption"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-11-29 21:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 21:06 Piotr Szymaniak [this message]
2012-11-30  6:09 ` A lot of NILFS: bad btree node messages (readonly fs) 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
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=20121129210650.GA4028@wloczykij \
    --to=szarpaj-tbom9ca2r9grdjvtcaxf/a@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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.