Linux NILFS development
 help / color / mirror / Atom feed
From: David Arendt <admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs error
Date: Sun, 19 Sep 2010 19:22:46 +0200	[thread overview]
Message-ID: <4C9646E6.4090009@prnet.org> (raw)
In-Reply-To: <20100919.213754.31465789.ryusuke-sG5X7nlA6pw@public.gmane.org>

  Hi,

there is one unimportant corrupted file. Is it safe to use the file 
system after removing this file or should I go the backup/restore route ?

Garbage collection was running when the problem appeared.

The disk is a 1tb disk and 16gb have been free.

Thanks in advance,
Bye,
David Arendt

On 09/19/10 14:37, Ryusuke Konishi wrote:
> Hi,
> On Sun, 19 Sep 2010 07:36:56 +0200, David Arendt wrote:
>>    Hi,
>>
>> yesterday I had the following error:
>>
>> Sep 18 18:03:24 server kernel: NILFS: bad btree node
>> (blocknr=226497086): level
>> = 37, flags = 0x18, nchildren = 22092
>> Sep 18 18:03:24 server kernel: NILFS error (device sdb1):
>> nilfs_truncate_bmap: b
>> map is broken (ino=69)
>> Sep 18 18:03:24 server kernel: Remounting filesystem read-only
>> Sep 18 18:03:24 server kernel: nilfs_palloc_commit_free_entry: entry
>> number 69 already freed
>>
>> Remounting the filesytem worked correctly. What could be the cause of
>> this error ?
> Thank you for the report.
>
> According to the log, nilfs detected btree corruption during file
> deletion; the message "bad btree node ..." shows a btree node block
> that nilfs read was broken.
>
> One possible cause is garbage collection, or there may be a problem
> with exclusion control on delete operation.  Or, the block might be
> actually broken if the underlying device is not reliable.
>
>
> Do you think nilfs_cleanerd worked before this trouble?
>
> How much free space was left on the device?
>
>> Should I preventively reformat the disk and recreate the
>> filesystem ?
> Yes, it's recommended for safety.  If you haven't yet reformatted the
> device, try the following command for sanity check.
>
>   # find /mount-dir -type f -exec cat {} \;>/dev/null
>
>
> Regards,
> Ryusuke Konishi
> --
> 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

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

  parent reply	other threads:[~2010-09-19 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19  5:36 nilfs error David Arendt
     [not found] ` <4C95A178.3020701-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2010-09-19 12:37   ` Ryusuke Konishi
     [not found]     ` <20100919.213754.31465789.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-09-19 17:22       ` David Arendt [this message]
     [not found]         ` <4C9646E6.4090009-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2010-09-20  7:44           ` Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2013-12-07  2:17 Jon Watte
     [not found] ` <CAJgyHGOeRhj7D4GeyfHhBjXLE3K40DiakT2Zms2D7TPB-BiRog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-07 10:34   ` Vyacheslav Dubeyko
     [not found]     ` <BA9C3894-7D2F-4FA1-88DE-E830102A0B5D-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-12-09 16:33       ` Jon Watte
     [not found]         ` <CAJgyHGMmxs8RUiFiZyJW2xNODuip_1yYkUTZ1_-VSPWivtHeSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-10  6:45           ` Vyacheslav Dubeyko
2013-12-10 16:47             ` Jon Watte
     [not found]               ` <CAJgyHGMKCwOKR9dZ6tfTr8j7vMaye94HsiWVZSYZ3Y=+P=HkYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-11  6:31                 ` Vyacheslav Dubeyko

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=4C9646E6.4090009@prnet.org \
    --to=admin-/lhds3kc8bfytjvyw6ydsg@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@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