public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: pushing out a new xfsprogs release,	was Re: [PATCH] xfsprogs: fix unaligned access in libxfs
Date: Sat, 29 Aug 2009 18:22:05 -0700	[thread overview]
Message-ID: <4A99D43D.5050208@sandeen.net> (raw)
In-Reply-To: <200908300017.07268@zmi.at>

Michael Monnerie wrote:
> On Freitag 28 August 2009 Christoph Hellwig wrote:
>> What do people thing about pushing out a 3.0.3 xfsprogs
>> release?
> 
> Is there the patch to repair my filesystem? I sent the metadump to Eric 
> once, I think he did some patches. Are they there, or do I need 
> something else also? I'm still having the problem, and would like to fix 
> it.
> 
> mfg zmi

Afraid I haven't fixed that one yet, sorry.  If you could open a bug on 
xfs.org's bugzilla it'd be much better for tracking ...

I did find that building xfsprogs w/o debug ASSERTs turned on, I could 
get a clean fs after 2 runs, just to get you going again...

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-30  1:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28 15:37 [PATCH] xfsprogs: fix unaligned access in libxfs Christoph Hellwig
2009-08-28 17:15 ` Eric Sandeen
2009-08-28 18:24   ` pushing out a new xfsprogs release, was " Christoph Hellwig
2009-08-28 21:20     ` Felix Blyakher
2009-08-29 22:17     ` Michael Monnerie
2009-08-30  1:22       ` Eric Sandeen [this message]
2009-08-30  8:44         ` Michael Monnerie
2009-08-28 21:39 ` Alex Elder
2009-08-28 22:15   ` Christoph Hellwig
2009-08-28 22:38     ` Alex Elder

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=4A99D43D.5050208@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=michael.monnerie@is.it-management.at \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox