From: John Robinson <john.robinson@anonymous.org.uk>
To: simonmcnair@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: removing AHCI SATA devices
Date: Wed, 23 Feb 2011 11:19:27 +0000 [thread overview]
Message-ID: <4D64ED3F.4050106@anonymous.org.uk> (raw)
In-Reply-To: <4D64C503.1080304@gmail.com>
On 23/02/2011 08:27, Simon McNair wrote:
> thanks Jeff. It just seems like a hit and miss solution (no way of
> knowing all data has been written to and that the device has been
> unmounted from all filesystems). I kinda expected some kind of 'it is
> safe to remove /dev/sdb' in dmesg.
I think `eject /dev/sdb` will do what you want - if it's safe to pull,
it'll exit immediately and silently, but if it or any of its partitions
are still associated with any filesystem or md device, and the drive
can't safely be ejected/unplugged, it'll complain.
Cheers,
John.
next prev parent reply other threads:[~2011-02-23 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 16:05 removing AHCI SATA devices Simon Mcnair
2011-02-22 21:36 ` Jeff Garzik
2011-02-23 8:27 ` Simon McNair
2011-02-23 10:54 ` hansbkk
2011-02-23 11:19 ` John Robinson [this message]
2011-02-23 16:21 ` Roberto Spadim
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=4D64ED3F.4050106@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=simonmcnair@gmail.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;
as well as URLs for NNTP newsgroup(s).