Re: A lot of NILFS: bad btree node messages (readonly fs)

[Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>]

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?

With the best regards,
Vyacheslav Dubeyko.


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html