| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | xfs_fsr not defragmenting: 'could not open tmp file' |
| From: | Richard Troxell <knavewave@xxxxxxxxx> |
| Date: | Thu, 12 Feb 2009 19:15:31 -0800 (PST) |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1234494931; bh=YEQ5n4O0smGroTk/a+8yVjTXTAiUXo/4Ko4XKOnY2LQ=; h=Message-ID:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=DL2XIAJ8F9Jt4UzllKq8hBVkHCK6Tnr79DzJ3k4bwrPK/byhL5vyabnj8mCdW6uhxvZa0JgPRDSXZigqWtOm/oTPSfWCEVJWJDbmsfjQO7Ye3rI1B71CtmsXFTmpZ8aW7qgFOMFDfBgUto5pzO/vCTwEYJqXKUfsVxVSbhmhtr0= |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=5Iy/FdsaRrP/5dMqrc1QH/cmA78xEMCbnDKHLIy6kdioynmmsorbNlCVRqCnbgCOLPblo60jIeKlxCHs3D+t+sJ9+CKxQsh8rEE1bSMRzsSLc+A3LX1/+HgiWJTb8zwqtpwaPHf1QmrvdYm+i80q5Ij3yABkFzjrxvEWmXBnaCE=; |
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!
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Does XFS support the sync mount option?, Eric Sandeen |
|---|---|
| Next by Date: | Re: BUG: soft lockup detected on CPU#1!, Eric Sandeen |
| Previous by Thread: | [XFS updates] XFS development tree branch, master, updated. v2.6.28-rc3-12990-g8aa4349, xfs |
| Next by Thread: | Re: xfs_fsr not defragmenting: 'could not open tmp file', Michael Monnerie |
| Indexes: | [Date] [Thread] [Top] [All Lists] |