Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org
Subject: Re: nilfs_check_page: bad entry in directory #37945
Date: Tue, 17 Mar 2009 00:23:33 +0900 (JST)	[thread overview]
Message-ID: <20090317.002333.93458556.ryusuke@osrg.net> (raw)
In-Reply-To: <20090317.000905.79144599.ryusuke-sG5X7nlA6pw@public.gmane.org>

On Tue, 17 Mar 2009 00:09:05 +0900 (JST), Ryusuke Konishi wrote:
> Hi David,
> On Mon, 16 Mar 2009 11:18:13 +0100, David Arendt wrote:
> > Hi,
> > 
> > this morning I discovered this in /var/log/messages
> > 
> > Mar 16 10:59:00 server NILFS error (device sda3): nilfs_check_page: bad
> > entry in directory #37945: unaligned directory entry - offset=0,
> > inode=1919250021, rec_len=14411, name_len=67
> >
> > I am using nilfs 2.0.10.
> > 
> > What should I do about this error ? Should I ignore it or should special
> > care be taken about it ?
> > 
> 
> offset=0 --> first entry of the directory.
> inode=1919250021 --> unnatural inode number. seems invalid.
> rec_len=14411 --> invalid.
> 
> So, this directory is completely broken. Maybe b-tree of the directory
> is pointing to a wrong block.
> 
> Is this reproducible by umount/mount and ls -R ?

The directory's inode number was shown in the log!
You can find it by:

 $ find /mount-dir -inum 37945 -ls


Regards,
Ryusuke Konishi

  parent reply	other threads:[~2009-03-16 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 10:18 nilfs_check_page: bad entry in directory #37945 David Arendt
     [not found] ` <49BE2765.2050200-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-03-16 10:49   ` Reinoud Zandijk
2009-03-16 15:09   ` Ryusuke Konishi
     [not found]     ` <20090317.000905.79144599.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-16 15:23       ` Ryusuke Konishi [this message]
     [not found]         ` <20090317.002333.93458556.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-16 22:17           ` David Arendt
     [not found]             ` <49BECFDF.1060802-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-03-17 11:06               ` Ryusuke Konishi
     [not found]                 ` <20090317.200609.69369815.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-17 11:16                   ` admin-/LHdS3kC8BfYtjvyW6yDsg

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=20090317.002333.93458556.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@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