On Mon, 11 Jun 2012, James Pearson wrote:
> What does:
>
> /usr/sbin/xfs_bmap -pl 10Gtest
>
> output (when run on the server)?
10Gtest:
0: [0..808319]: 261386472..262194791 808320 blocks
1: [808320..1357951]: 273699584..274249215 549632 blocks
2: [1357952..2406527]: 307386624..308435199 1048576 blocks
3: [2406528..2631927]: 308443904..308669303 225400 blocks
4: [2631928..4728959]: 1279691136..1281788167 2097032 blocks
5: [4728960..7704575]: 5285370624..5288346239 2975616 blocks
6: [7704576..8928511]: 5333860864..5335084799 1223936 blocks
7: [8928512..11709047]: 5219053184..5221833719 2780536 blocks
8: [11709048..14365431]: 3943770240..3946426623 2656384 blocks
9: [14365432..16899703]: 4437210880..4439745151 2534272 blocks
10: [16899704..17327103]: 4449971968..4450399367 427400 blocks
11: [17327104..18992639]: 3578345984..3580011519 1665536 blocks
12: [18992640..20356767]: 4200870752..4202234879 1364128 blocks
13: [20356768..20479999]: 4833581696..4833704927 123232 blocks
>
> You can also 'recover' the lost space by running (as root on the server):
>
> /usr/sbin/xfs_fsr 10Gtest
doesn't help :
]# xfs_fsr 10Gtest
]# du -hs
17G .
I'm also running xfs_fsr /dev/VolGroup01/LogVol00 weekly, which doesn't
help.
> P.S. you can also see the allocated size of a file using the -s option to ls
Thanks, this shows the same info as du.
Stephan