From: Jim Paris <jim@jtan.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Richard Scobie <r.scobie@clear.net.nz>, linux-ide@vger.kernel.org
Subject: Re: Port multiplier
Date: Mon, 28 Aug 2006 11:35:54 -0400 [thread overview]
Message-ID: <20060828153554.GA4471@jim.sh> (raw)
In-Reply-To: <44F2EA27.9090603@gmail.com>
Tejun Heo wrote:
> Richard Scobie wrote:
>
> >Can I unmount the connected and mounted array and just unplug the array
> >with no further concern?
>
> The machine will survive and detach the device correctly but
> yet-unwritten data will be lost.
He said he'll unmount it first, so presumably that should avoid most
data loss? I suppose if you're in the middle of a RAID resync, or
just ran fdisk or fsck or similar, you could still have unflushed
data. Does that mean that hot-unplug is not recommended, and one
should always do warm-unplug instead?
-jim
next prev parent reply other threads:[~2006-08-28 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 7:16 Port multiplier Richard Scobie
2006-08-28 13:05 ` Tejun Heo
2006-08-28 15:35 ` Jim Paris [this message]
2006-08-28 15:38 ` Tejun Heo
2006-08-29 7:02 ` Richard Scobie
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=20060828153554.GA4471@jim.sh \
--to=jim@jtan.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=r.scobie@clear.net.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).