| To: | Ludek Finstrle <ludek.finstrle@xxxxxxxxxx> |
|---|---|
| Subject: | Re: ls -l versus du -sk after xfs_fsr |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Tue, 04 Oct 2005 14:37:26 -0500 |
| Cc: | Mathieu Betrancourt <mbetrancourt@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20051004190338.GA15263@xxxxxxxxxxxxxxxxx> |
| References: | <20050926071451.GA3751@xxxxxxxxxxxxxxxxx> <4338128F.8000707@xxxxxxx> <20050927163531.GA19652@xxxxxxxxxxxxxxxxx> <433976C5.1000104@xxxxxxx> <20050929054410.GA30789@xxxxxxxxxxxxxxxxx> <20051001091130.GA15808@xxxxxxxxxxxxxxxxx> <434174A7.6010904@xxxxxxx> <26743c10510031244x726ff508m89ecd0398417e521@xxxxxxxxxxxxxx> <4341E780.70803@xxxxxxx> <20051004190338.GA15263@xxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0 (X11/20041206) |
Ludek Finstrle wrote: Here's the output of xfs_info for the problematic one :Here is my xfs_info: # xfs_info /dev/md9 meta-data=/ isize=256 agcount=8, agsize=163856 blks= sectsz=512 data = bsize=4096 blocks=1310752, imaxpct=25 Ok, nothing odd about isize, sectsize, bsize.... thanks. It would also be interesting to see the xfs_repair output, and xfs_bmap (-v and -a) output of the problematic files prior to running xfs_fsr, if possible.I don't know which files will be problematic after xfs_fsr. Ah, I suppose not :) I'm sorry, I don't have enough time till Friday. Then I'll try to play with the problem. Thanks, I appreciate it... we're trying to reproduce it here. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ls -l versus du -sk after xfs_fsr, Ludek Finstrle |
|---|---|
| Next by Date: | Re: ls -l versus du -sk after xfs_fsr, Eric Sandeen |
| Previous by Thread: | Re: ls -l versus du -sk after xfs_fsr, Ludek Finstrle |
| Next by Thread: | Re: ls -l versus du -sk after xfs_fsr, Ludek Finstrle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |