From: "Marcin Mirosław" <marcin@mejor.pl>
To: xfs@oss.sgi.com
Subject: Re: Enabling lazy counters damages filesystem
Date: Thu, 29 Apr 2010 10:03:37 +0200 [thread overview]
Message-ID: <4BD93D59.2010506@mejor.pl> (raw)
In-Reply-To: <20100429020549.GC2512@dastard>
W dniu 29.04.2010 04:05, Dave Chinner pisze:
> Yeah, you are right. I was thinking that xfs_db did the feature bit
> modifications, then repair just fixed up the accounting. but repair
> does both in this case. I should remember code that I wrote years
> ago, but for some reason it all seems to be a little bit hazy...
>
> Let me go look at your repair patch again ;)
Hi,
Eric, Dave, thank you for quick replay and patch. Patch solves problem
for me:)
Regards!
Marcin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-29 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 14:34 Enabling lazy counters damages filesystem Marcin Mirosław
2010-04-28 21:40 ` Eric Sandeen
2010-04-28 23:04 ` Dave Chinner
2010-04-29 1:43 ` Dave Chinner
2010-04-29 1:51 ` Eric Sandeen
2010-04-29 2:05 ` Dave Chinner
2010-04-29 8:03 ` Marcin Mirosław [this message]
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=4BD93D59.2010506@mejor.pl \
--to=marcin@mejor.pl \
--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