On Thu, Sep 10, 2015 at 08:52:20PM +0300, Tapani Tarvainen (tapani@xxxxxxxxxxxxxxxxxx) wrote: > Also, it turns out I have another similar case: another filesystem > (in the same RAID set) failed also, even though it'd initially > mounted without problems. Now it shows the same symptoms, > neither mount nor repair works (have't tried repair -L yet). Apparently it only failed after someone tried to write on it. Potentially interesting stuff from dmesg: [31604.130052] XFS (dm-4): xfs_da_do_buf: bno 8388608 dir: inode 964 [31604.130080] XFS (dm-4): [00] br_startoff 8388608 br_startblock -2 br_blockcount 1 br_state 0 [31604.130126] XFS (dm-4): Internal error xfs_da_do_buf(1) at line 2011 of file /build/linux-4wkEzn/ linux-3.2.68/fs/xfs/xfs_da_btree.c. Caller 0xffffffffa0371b67 [31604.130127] [31604.130213] Pid: 18082, comm: du Not tainted 3.2.0-4-amd64 #1 Debian 3.2.68-1+deb7u1 [...] -- Tapani Tarvainen _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
