All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinoud Zandijk <reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: nilfs_check_page: bad entry in directory #37945
Date: Mon, 16 Mar 2009 11:49:32 +0100	[thread overview]
Message-ID: <20090316104932.GA7773@aardappel.13thmonkey.org> (raw)
In-Reply-To: <49BE2765.2050200-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>

Dear David,

On Mon, Mar 16, 2009 at 11:18:13AM +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

Fun! the offset is fine but i think it complains about the record length...
sounds like a bug to me, but others might shed more light on it. On the
question if it can be harmfull, well maybe on directory appending but even so
it might autocorrect(ed) it?

With regards,
Reinoud

  parent reply	other threads:[~2009-03-16 10:49 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 [this message]
2009-03-16 15:09   ` Ryusuke Konishi
     [not found]     ` <20090317.000905.79144599.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-16 15:23       ` Ryusuke Konishi
     [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=20090316104932.GA7773@aardappel.13thmonkey.org \
    --to=reinoud-s783fymb3ccdnm+yrofe0a@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 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.