All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Cc: David Chinner <dgc@sgi.com>, Timothy Shimmin <tes@sgi.com>,
	ck@vds.kolivas.org
Subject: Re: xfs_fsr and null byte areas in files
Date: Sun, 12 Aug 2007 22:29:40 +0200	[thread overview]
Message-ID: <200708122229.40400.Martin@lichtvoll.de> (raw)
In-Reply-To: <200707262309.24012.Martin@lichtvoll.de>

Am Donnerstag 26 Juli 2007 schrieb Martin Steigerwald:
> Am Dienstag 10 Juli 2007 schrieb David Chinner:
> > > 1) Is there an XFS qa test available for xfs_fsr? If so I could use
> > > that one. Are there some hints on how to get started on XFS qa?
> >
> > Yes, test 042. Download it from CVS, build it (installing all the
> > bits it asks for ;), edit common.config to add your test and scratch
> > partitions (both volatile) and the 'check -l 042' to run test 042.
>
> Hi!
>
> I ran test 42 and it completes successfully.

Hello,

I now read a post from someone who faced null byte areas in files after 
xfs_fsr as well[1]. And he writes that this problem is related to the ck 
patchset:

http://bhhdoa.org.au/pipermail/ck/2007-August/008433.html

It may well be that it is related to the ck patchset in my case as well. I 
did not know the exact kernel version anymore when I was using xfs_fsr, 
since it took me 2 weeks to actually find about this corruption. Well and 
when I ran xfsqa test I had a slighly newer kernel was using the CFS 
scheduler instead of the ck patchset. Actually I thought the other was 
using the CFS scheduler as well  I didn't think of it as having any 
relevance so I didn't look into that direction.

But now it seems that the problem actually is related ck patchset and that 
I was using a kernel with ck patchset as well. I try to find the time to 
run xfsqa test 42 for my latest ck patchset kernel to know for sure.

I just wanted you to know. It seems to me that this may well not been a 
problem with XFS at all.

[1] http://oss.sgi.com/archives/xfs/2007-07/msg00038.html

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

  reply	other threads:[~2007-08-12 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 21:13 Fwd: xfs_fsr and null byte areas in files (REPOST) / file data checksumming Martin Steigerwald
2007-07-10  0:50 ` David Chinner
2007-07-10  3:53   ` Timothy Shimmin
2007-07-10 15:48     ` Eric Sandeen
2007-07-26 21:09   ` xfs_fsr and null byte areas in files Martin Steigerwald
2007-08-12 20:29     ` Martin Steigerwald [this message]
2007-08-13 17:25       ` Martin Steigerwald
2007-08-13 17:45         ` [ck] " Felix X
2007-07-26 21:44   ` 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=200708122229.40400.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=ck@vds.kolivas.org \
    --cc=dgc@sgi.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=tes@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.