All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Stor?? <289471341@qq.com>, Jeff Liu <jeff.liu@oracle.com>,
	xfs@oss.sgi.com
Subject: Re: [xfs_check Out of memory: ]
Date: Mon, 30 Dec 2013 12:27:43 +0100	[thread overview]
Message-ID: <20131230112743.GA16889@citd.de> (raw)
In-Reply-To: <52C0D281.7040704@hardwarefreak.com>

On 29.12.2013 19:55, Stan Hoeppner wrote:
> On 12/29/2013 3:50 AM, Dave Chinner wrote:
> ...
> > I think you are forgetting that developer time is *expensive* and
> > *scarce*. This is essentially a solved problem: An SSD in a USB3
> > enclosure as a temporary swap device is by far the most cost
> > effective way to make repair scale to arbitrary amounts of metadata.
> > It certainly scales far better than developer time and testing
> > resources...
> 
> Now this is an interesting idea Dave.  I hadn't considered temporary
> swap.  Would USB be reliable enough for this?  I've seen lots problem
> reports with folks using USB storage with Linux, random disconnections
> and what not.

It's certainly a problem with several variables.
- Quality of USB-Stack (should be quite good nowadays, but there can 
always be (new) bugs)
- Quality of SATA <-> USB(3) Chip
- Quality of SSD itself

And with Quality i mean everything from physical chip up to firmware.

I'm not quite sure what happens when SWAP crapps out. I think it can be 
everything from "machine goes dead" down to "all programs with pages in 
swap are terminated".

I've transfert quite a few TB over USB3 and i can say, it mostly works. 
But random disconnects happen and you can't really be sure which part is 
the problem as it only happens rarely.

For e.g. currently i have a HDD that randomly but seldomly craps out in 
an USB3 enclosure, after coping a few hundert GB. The drive works 
flawlessly when connected directly by SATA to a (different) computer, at 
least i haven't had a failure after i moved the drive. Is it the drive, 
chip in enclose, firmware between HDD & enclosure not playing nice (like 
too high command timeouts on HDD side and too low on enclosure-sde), 
USB3 stack. Can't really tell.

So:
I would consides SWAP on a device connected via USB3 to be on the risky 
side.

I would validate beforehand if that specific combination of 
xhci/enclosure chip/SSD survies a prolonged time of "high I/O stress".
Like several days of full bandwidth/random I/O.




-- 

Matthias

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

  reply	other threads:[~2013-12-30 11:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27  6:48 [xfs_check Out of memory: ] Stor??
2013-12-27  7:41 ` Jeff Liu
2013-12-27  8:07   ` Arkadiusz Miśkiewicz
2013-12-27 22:42     ` Dave Chinner
2013-12-27 23:20       ` Arkadiusz Miśkiewicz
2013-12-28 16:55         ` Stan Hoeppner
2013-12-28 17:35           ` Jay Ashworth
2013-12-28 22:01             ` Stan Hoeppner
2013-12-28 23:39           ` Arkadiusz Miśkiewicz
2013-12-29  0:54             ` Stan Hoeppner
2013-12-29 11:23               ` Arkadiusz Miśkiewicz
2013-12-29  9:50         ` Dave Chinner
2013-12-29 11:57           ` Arkadiusz Miśkiewicz
2013-12-29 23:27             ` Dave Chinner
2013-12-30  1:55           ` Stan Hoeppner
2013-12-30 11:27             ` Matthias Schniedermeyer [this message]
2013-12-30 13:19             ` Roger Willcocks
2013-12-30 16:25               ` Stan Hoeppner
2013-12-30 17:19             ` Stefan Ring

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=20131230112743.GA16889@citd.de \
    --to=ms@citd.de \
    --cc=289471341@qq.com \
    --cc=jeff.liu@oracle.com \
    --cc=stan@hardwarefreak.com \
    --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 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.