Skip to contentSkip to conversation

xfs_fsr not defragmenting: 'could not open tmp file'

DISCUSSION Richard Troxell 3 participants 3 messages Feb 13, 2009

lore
Share & tools
lore
#0 lore raw

I am trying out the xfs_fsr utility, but am not having much luck getting it to actually do anything. Running with -vd, I see a flood of 'no such file messages' like the following.

ino=570425612
ino=570425612 extents=12 can_save=11 tmp=/disk08-01/.fsr/ag329/tmp22898 could not open tmp file: /disk08-01/.fsr/ag329/tmp22898: No such file or directory

Just for the fun of it, I tried creating some of these directories, only to find the operation bails in the ioctl. ino=570425630
ino=570425630 extents=13 can_save=12 tmp=/disk08-01/.fsr/ag328/tmp22898
DEBUG: fsize=445760 blsz_dio=445440 d_min=512 d_max=2147483136 pgsz=4096
Temporary file has 1 extents (13 in original)
XFS_IOC_SWAPEXT failed: ino=570425630: Invalid argument

xfs_fsr is coming from xfsprogs 3.0.0
Linux kernel is 2.6.23.9
Architecture is x86_64, but xfs_fsr is 32bit.

I did some searching for through past post for any similiar cases, but could not find any. Here are some other useful outputs that I found from somewhat related posts.

# xfs_db -c frag -f /dev/sdp2
actual 38348, ideal 1318, fragmentation factor 96.56%

Most of the files appear to have single extent layouts, but there are a few exceptions.

# xfs_db -c "frag -v" -f /dev/sdp2 
...
inode 570425622 actual 957 ideal 1
...

I did a quick check of the 'bmap' of the inode listed above and the file looks non-sparse (all 'flag 0')

Thanks!

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#1 lore raw
Quoted 3 lines · On Freitag 13 Februar 2009 Richard Troxell wrote:

xfs_fsr is coming from xfsprogs 3.0.0
Linux kernel is 2.6.23.9
Architecture is x86_64, but xfs_fsr is 32bit.

I'm not a dev, but I'd suggest trying the newest 2.6.28 kernel and see if the problem persists. There have been many fixes since your kernel.

mfg zmi

Signature · 10 lines
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
#2 lore raw
Quoted 9 lines · Michael Monnerie
Quoted 3 lines · On Freitag 13 Februar 2009 Richard Troxell wrote:

xfs_fsr is coming from xfsprogs 3.0.0
Linux kernel is 2.6.23.9
Architecture is x86_64, but xfs_fsr is 32bit.

I'm not a dev, but I'd suggest trying the newest 2.6.28 kernel and see if the problem persists. There have been many fixes since your kernel.

mfg zmi

Actually, yes. there were 32/64 issues until recently, and fsr was in fact using an ioctl that did not have a 32-bit handler. These weren't fixed until 2.6.29-rc1.

-Eric

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs