All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Neil Brown <neilb@suse.de>, Steven Ellis <steven@openmedia.co.nz>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Any benefity to write intent bitmaps on Raid1
Date: Sat, 11 Apr 2009 09:08:39 -0400	[thread overview]
Message-ID: <49E09657.4020809@tmr.com> (raw)
In-Reply-To: <877i1rpogf.fsf@frosties.localdomain>

Goswin von Brederlow wrote:
> Neil Brown <neilb@suse.de> writes:
>   
>
>> You could make it work, but there would be a performance hit.
>>
>> Now look at your cases where a filesystem doesn't work well:
>>  1/ Swap.  That is a non-issue.  After a crash, the contents of swap
>>     are irrelevant.  Without a crash, the races you refer to are
>>     irrelevant.
>>     
>
> What about suspend to swap?
>   

suspend is a "without a crash" case, I wouldn't want to restore from 
swap if the system failed to complete a clean shutdown.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.



  reply	other threads:[~2009-04-11 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  0:24 Any benefity to write intent bitmaps on Raid1 Steven Ellis
2009-04-09  1:30 ` Bryan Mesich
2009-04-09  5:59 ` Neil Brown
2009-04-09  6:26   ` Goswin von Brederlow
2009-04-10  9:04     ` Neil Brown
2009-04-11  2:56       ` Goswin von Brederlow
2009-04-11  5:35         ` Neil Brown
2009-04-11  8:46           ` Goswin von Brederlow
2009-04-11 13:08             ` Bill Davidsen [this message]
2009-04-09 22:51   ` Bill Davidsen
2009-04-10  9:10     ` Neil Brown

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=49E09657.4020809@tmr.com \
    --to=davidsen@tmr.com \
    --cc=goswin-v-b@web.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=steven@openmedia.co.nz \
    /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.