Reinoud Zandijk skrev 2013-06-06 11:20:
Hi,
just my $0.02 so to say:
On Thu, Jun 06, 2013 at 10:56:09AM +0400, Vyacheslav Dubeyko wrote:
First of all, unfortunately, I can't reproduce the issue yet, currently.
I suspect that in this issue the aging state of volume, peculiarity of
workload and environment play very important role. As I remember, all
reporters of likewise symptoms (broken bnode error messages) talked
about several months of successful working of NILFS2 file system.
sounds to me as if a b-tree is in a perculiar state and that updating the
btree results in this corruption.
Have you tried to mount one of the checkpoints/snapshots earlier as RO and see
if those are correct? If so, dumping both DATs and both btrees might give a
clue as to what went wrong. If only it gives a clue as to how complicated the
btree is before the updating and what actions are taken on it.
With regards,
Reinoud
I have configured nilfs_cleanerd.conf to clean very aggressively so my
earliest checkpoint is from after the incident. I included the contents
of that file in my first email sent on May 22
(http://article.gmane.org/gmane.comp.file-systems.nilfs.user/2920).
Even so, I tried to loopback mount the oldest checkpoint I have which I
found was affected by the same corruption.
# losetup /dev/loop0 /Athena/Dump/riven/riven-home-20130531.img
# mount /dev/loop0 /mnt
$ mount | tail -1
/dev/loop0 on /mnt type nilfs2 (ro,relatime,norecovery)
$ lscp /dev/loop0
CNO DATE TIME MODE FLG NBLKINC ICNT
1260571 2013-05-23 16:51:49 cp - 140 155496
1260572 2013-05-23 16:51:51 cp - 1632 155495
1260575 2013-05-23 16:52:06 cp - 1473 155496
1260576 2013-05-23 16:52:09 cp - 49 155495
1260580 2013-05-24 23:36:11 cp - 1345 155496
1260581 2013-05-24 23:36:16 cp - 1500 155495
1260582 2013-05-24 23:36:21 cp - 1356 155497
1260583 2013-05-24 23:36:26 cp - 1465 155495
# chcp ss /dev/loop0 1260571
# umount /mnt
# mount -o ro,norecovery,cp=1260571 /dev/loop0 /mnt
$ cd /mnt/anton/Bilder/20130321-28\ Jakobs\ bilder\ från\ Nederländerna
$ LANG=C cat *>/dev/null
cat: 160.JPG: Input/output error
cat: 163.JPG: Input/output error
cat: 164.JPG: Input/output error
cat: 165.JPG: Input/output error
cat: 170.JPG: Input/output error
cat: 172.JPG: Input/output error
cat: 179.JPG: Input/output error
--
Best Regards,
Anton Eliasson
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
