Skip to contentSkip to conversation

nilfs error

DISCUSSION David Arendt 2 participants 4 messages Sep 19, 2010 – Sep 20, 2010 3 messages not in the archive NILFS2 filesystem

lore
Share & tools
lore

David Arendt

author
#0 lore raw

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 ? Should I preventively reformat the disk and recreate the filesystem ?

Thanks in advance
Bye,
David Arendt
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
In reply to a message not in the archive

Hi,

Quoted 12 lines · David Arendt

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
Quoted 4 lines

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?

Quoted 2 lines

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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#4 lore raw
In reply to a message not in the archive

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

Quoted 41 lines · Ryusuke Konishi

Hi,

Quoted 12 lines · David Arendt
   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
Quoted 4 lines

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?

Quoted 2 lines

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
Quoted 6 lines

Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
In reply to a message not in the archive

Hi,

Quoted 4 lines · David Arendt

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 ?

Making backup is of course recommended.

But if you don't mind, continue using it. It may give us sort of a clue, for instance, whether the corruption is restrictive (or temporary, etc).

Quoted 3 lines

Garbage collection was running when the problem appeared.

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

Well, there may be something missed between garbage collection and file deletion. Will recheck.

Thanks,
Ryusuke Konishi

Quoted 53 lines

Thanks in advance,
Bye,
David Arendt

Quoted 41 lines · Ryusuke Konishi

Hi,

Quoted 12 lines · David Arendt
   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
Quoted 4 lines

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?

Quoted 2 lines

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
Quoted 6 lines

Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 4 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html