<div dir="ltr">[/mnt/xfsd/lost+found]# pwd<br>/mnt/xfsd/lost+found<br>[ /mnt/xfsd/lost+found]# ls -l<br>total 0<br>-rw-r--r-- 1 root root 0 Feb 1 19:18 6235944<br>[ /mnt/xfsd/lost+found]# sudo getfattr -m . -d -e hex 6235944<br>
[ /mnt/xfsd/lost+found]# <br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/10 符永涛 <span dir="ltr"><<a href="mailto:yongtaofu@gmail.com" target="_blank">yongtaofu@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>Here's the file info in lost+found:<br><br>[ lost+found]# pwd<br>/mnt/xfsd/lost+found<br>[ lost+found]# ls -l<br>总用量 4<br>---------T 1 root root 0 2月 28 15:42 3097<br>---------T 1 root root 0 2月 28 15:16 6169<br>
[<a href="mailto:root@10.15.136.67" target="_blank">root@10.15.136.67</a> lost+found]# sudo getfattr -m . -d -e hex 6169<br>[<a href="mailto:root@10.15.136.67" target="_blank">root@10.15.136.67</a> lost+found]# sudo getfattr -m . -d -e hex 3097<br>
# file: 3097<br>
trusted.afr.ec-data-client-2=0x000000000000000000000000<br>trusted.afr.ec-data-client-3=0x000000000000000000000000<br>trusted.afr.ec-data1-client-2=0x000000000000000000000000<br>trusted.afr.ec-data1-client-3=0x000000000000000000000000<br>
trusted.gfid=0x2bb701d327c44bb0af78d69e89f192a4<br>trusted.glusterfs.dht.linkto=0x65632d64617461312d7265706c69636174652d3400<br>trusted.glusterfs.quota.b8e8b3ef-0268-40af-93b6-257c4c7ef17a.contri=0x0000000004249000<br><br>
<br></div>It seems they're some link files for glusterfs dht xlator.<br><br></div>Thank you.<br></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">2013/4/10 Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net" target="_blank">sandeen@sandeen.net</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 4/9/13 10:18 AM, 符永涛 wrote:<br>
</div><div>> The servers are back to service now and It's hard to run xfs_repair. It always happen bellow is the xfs_repair log when it happens on another server several days ago.<br>
<br>
</div><div><div>...<br>
<br>
> 第二步<br>
> repair的log<br>
><br>
> sh-4.1$ sudo xfs_repair /dev/glustervg/glusterlv<br>
> Phase 1 - find and verify superblock…<br>
> Phase 2 - using internal log<br>
> - zero log…<br>
> - scan filesystem freespace and inode maps…<br>
> agi unlinked bucket 0 is 4046848 in ag 0 (inode=4046848)<br>
> agi unlinked bucket 5 is 2340485 in ag 0 (inode=2340485)<br>
> agi unlinked bucket 6 is 2326854 in ag 0 (inode=2326854)<br>
> agi unlinked bucket 8 is 1802120 in ag 0 (inode=1802120)<br>
> agi unlinked bucket 14 is 495566 in ag 0 (inode=495566)<br>
> agi unlinked bucket 16 is 5899536 in ag 0 (inode=5899536)<br>
> agi unlinked bucket 19 is 4008211 in ag 0 (inode=4008211)<br>
> agi unlinked bucket 21 is 4906965 in ag 0 (inode=4906965)<br>
> agi unlinked bucket 23 is 2022231 in ag 0 (inode=2022231)<br>
> agi unlinked bucket 24 is 1626200 in ag 0 (inode=1626200)<br>
> agi unlinked bucket 25 is 938585 in ag 0 (inode=938585)<br>
> agi unlinked bucket 30 is 4226526 in ag 0 (inode=4226526)<br>
> agi unlinked bucket 34 is 4108962 in ag 0 (inode=4108962)<br>
> agi unlinked bucket 37 is 1740389 in ag 0 (inode=1740389)<br>
> agi unlinked bucket 39 is 247399 in ag 0 (inode=247399)<br>
> agi unlinked bucket 40 is 6237864 in ag 0 (inode=6237864)<br>
> agi unlinked bucket 43 is 3404331 in ag 0 (inode=3404331)<br>
> agi unlinked bucket 45 is 2092717 in ag 0 (inode=2092717)<br>
> agi unlinked bucket 48 is 4041008 in ag 0 (inode=4041008)<br>
> agi unlinked bucket 50 is 1459762 in ag 0 (inode=1459762)<br>
> agi unlinked bucket 56 is 852024 in ag 0 (inode=852024)<br>
<br>
</div></div>If this machine is still around in similar state, can you do a<br>
<br>
# find /path/to/mount -inum $INODE_NUMBER<br>
<br>
for the inode numbers above, and see what files they are?<br>
That might give us a clue about what operations were happening<br>
to them. Dumping the gluster xattrs on those files<br>
might also be interesting. Just guesses here, but it'd be a<br>
little more data.<br>
<br>
(if this is an old repair, maybe doing the same for your most<br>
recent incident would be best)<br>
<br>
Thanks,<br>
-Eric<br>
<div><br>
> - found root in ode chunk<br>
> Phase 3 - for each AG…<br>
> - scan and clear agi unlinked lists…<br>
> - process known inodes and perform inode discovery…<br>
> - agno = 0<br>
> 7f8220be6700: Badness in key lookup (length)<br>
> bp=(bno 123696, len 16384 bytes) key=(bno 123696, len 8192 bytes)<br>
<br>
</div>(FWIW the above warnings look like an xfs_repair bug, not related)<br>
<span><font color="#888888"><br>
-Eric<br>
<br>
</font></span></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>符永涛
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>符永涛
</div>