mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Pavel Machek <pavel@suse.cz>
Cc: smartmontools-support@lists.sourceforge.net,
	smartmontools-database-owner@lists.sourceforge.net,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, xfs@oss.sgi.com,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: Intel X25-E running Linux using XFS
Date: Fri, 12 Dec 2008 15:23:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0812121516190.17857@p34.internal.lan> (raw)
In-Reply-To: <20081212185803.GE11974@elf.ucw.cz>



On Fri, 12 Dec 2008, Pavel Machek wrote:

>
> Hi!
>
>> Due to the 100k write cycle lifetime, I will not be performing any more
>> benchmarks on the SSD itself, such benchmarks are available on
>> techreport.com but just wanted to send out the smart data for the
>> smartmontools list and point out it is working with linux+ich7+xfs.
>>
>> Overall, whenever I do anything now its just like the entire machine is
>> sitting in a ramdisk (similar when you boot knoppix and load to ramdisk).
>>
>> The techreport benchmarks are here:
>> http://techreport.com/articles.x/15931
>
> Actually I'd like to know... how does it behave during powerfails
> while it is being written to?
>
> Flashes I seen (USB / SD) developed bad sectors in that case, and
> ext2/ext3 can't handle that. (And I don't think xfs can handle that
> either).

I have a UPS for all of my machines, so that will not be a problem in my 
case.  I do not wish to trash a $720 SSD or my current install, if someone 
else wants to try feel free though :)

With barriers, presumably it would be safe-- but as always, a UPS/and 
barriers and/or RAID, there is no excuse not to have regular backups 
incase of a failure at any time..

I do recall however one instance where there was an apt-get dist-upgrade 
going and the power was cut to a machine on purpose (before/not 
using barriers) and suffice to say-- it got mucked/suffered many corruptions
all over the place.

Justin.

  reply	other threads:[~2008-12-12 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 21:54 Justin Piszcz
2008-12-12 18:58 ` Pavel Machek
2008-12-12 20:23   ` Justin Piszcz [this message]
2008-12-13 11:43     ` Stefan Richter
2008-12-22  8:50   ` Christoph Hellwig

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=alpine.DEB.1.10.0812121516190.17857@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=ap@solarrain.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=smartmontools-database-owner@lists.sourceforge.net \
    --cc=smartmontools-support@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®