All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: xfs_fsr - problem with open files possible?
Date: Fri, 15 Jun 2007 22:04:34 +0200	[thread overview]
Message-ID: <200706152204.34506.Martin@lichtvoll.de> (raw)
In-Reply-To: <200706152013.52836.Martin@lichtvoll.de>

Am Freitag 15 Juni 2007 schrieb Martin Steigerwald:

> Hello Eric!
>
> Well also from the man page as I just found out after sending my mail:
>
> "xfs_fsr  can  be  called with one or more arguments naming filesystems
> (block device name), and files to reorganize.  In this mode xfs_fsr
> does not read or write /var/tmp/.fsrlast_xfs nor does it run for a
> fixed time interval.  It makes  one pass through each specified regular
> file and all regular files in each specified filesystem.  A command
> line name referring to a symbolic link (except to a file system
> device), FIFO, or UNIX domain socket generates a warning  message,  but
> is otherwise ignored.  While traversing the filesystem these types of
> files are silently skipped."
>
> So maybe something along the lines of:
>
> xfs_fsr ~/Mail/.trash.index
>
> while it is open by KMail should be enough. I think I will give this a
> try soon.

Hello!

Hmmm, could not reproduce it with a single file. xfs_fsr seems to be 
behaving correctly:

shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
xfs_bmap -v .Kernel.index
.Kernel.index:
 EXT: FILE-OFFSET      BLOCK-RANGE        AG AG-OFFSET          TOTAL
   0: [0..167]:        83985960..83986127 15 (1586760..1586927)   168
   1: [168..175]:      83985824..83985831 15 (1586624..1586631)     8
shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index

Started Kontact (KMail)...

shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> lsof .Kernel.index
COMMAND   PID   USER   FD   TYPE DEVICE  SIZE      NODE NAME
kontact 15985 martin  mem    REG    8,2 86497 254828298 .Kernel.index
kontact 15985 martin   23u   REG    8,2 86497 254828298 .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
cp -a .Kernel.index .Kernel.index.old
shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
md5sum .Kernel.index.old
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index.old
shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index

Trying to defragment while file is open: xfs_fsr seems to leave the file 
alone completely like it should.

shambala:Mail/.Lichtvoll.directory/.Linux.directory> xfs_fsr .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
xfs_bmap -v .Kernel.index
.Kernel.index:
 EXT: FILE-OFFSET      BLOCK-RANGE        AG AG-OFFSET          TOTAL
   0: [0..167]:        83985960..83986127 15 (1586760..1586927)   168
   1: [168..175]:      83985824..83985831 15 (1586624..1586631)     8
shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index

Also on a second try

shambala:Mail/.Lichtvoll.directory/.Linux.directory> xfs_fsr .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
xfs_bmap -v .Kernel.index
.Kernel.index:
 EXT: FILE-OFFSET      BLOCK-RANGE        AG AG-OFFSET          TOTAL
   0: [0..167]:        83985960..83986127 15 (1586760..1586927)   168
   1: [168..175]:      83985824..83985831 15 (1586624..1586631)     8
shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index

Stopping Kontact (KMail) and trying to defragment then... well now it 
defragments. md5sum stays the fine.

shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> xfs_fsr .Kernel.index
shambala:Mail/.Lichtvoll.directory/.Linux.directory> 
xfs_bmap -v .Kernel.index
.Kernel.index:
 EXT: FILE-OFFSET      BLOCK-RANGE        AG AG-OFFSET          TOTAL
   0: [0..175]:        86612448..86612623 15 (4213248..4213423)   176
shambala:Mail/.Lichtvoll.directory/.Linux.directory> md5sum .Kernel.index
9d1fdd1138e297fd97548a3a4696e308  .Kernel.index


Hmmm, maybe there is some race condition that is not triggered always. If 
I find time I let xfs_fsr run von ~/Mail or folder with several sub 
folders so that more index files are touched. I can make a backup, let it 
run and if Kontact / KMail complains look at the differences.

Regards,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2007-06-15 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15 16:04 xfs_fsr - problem with open files possible? Martin Steigerwald
2007-06-15 16:58 ` Eric Sandeen
2007-06-15 18:13   ` Martin Steigerwald
2007-06-15 20:04     ` Martin Steigerwald [this message]
2007-06-23 15:23   ` xfs_fsr and null byte areas in files (was: Re: xfs_fsr - problem with open files possible?) Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200706152204.34506.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.