From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: ERROR: error removing the device '/dev/sdXN' - Inappropriate ioctl for device
Date: Wed, 01 Apr 2015 18:28:23 +0100 [thread overview]
Message-ID: <mfh9rn$2if$1@ger.gmane.org> (raw)
In-Reply-To: <551BEF67.3040305@oracle.com>
Anand,
Thanks for picking up.
The devid option sounds good.
Thanks,
Martin
On 01/04/15 14:15, Anand Jain wrote:
>
>
> Looks like an option to use devid to delete a device would
> have mitigated the issue. Also the error reported is no
> where near the reality. Will fix them.
>
> Thanks for reporting.
>
> Anand
>
>
> On 04/01/2015 06:54 PM, Martin wrote:
>> On 01/04/15 08:06, Anand Jain wrote:
>>>
>>>>>> btrfs device delete /dev/sdf5 /mnt/data2
>>>>>>
>>>>>> ERROR: error removing the device '/dev/sdf5' - Inappropriate ioctl
>>>>>> for
>>>>>> device
>>>
>>> very strange. 'btrfs fi show -m' shows btrfs fs(s) that are mounted.
>>
>> Looks like my /dev/sdf isn't responding with anything useful at all... A
>> firmware crash?... (This is for a 256GB SSD.)
>>
>>
>> # btrfs fi show -m
>>
>> [...]
>>
>> Label: 'btrfs_data2' uuid: 3aaee716-b98b-4c86-ba5a-53456994f152
>> Total devices 3 FS bytes used 159.31GiB
>> devid 1 size 206.47GiB used 206.02GiB path /dev/sdb5
>> devid 2 size 206.47GiB used 206.47GiB path /dev/sdd5
>> devid 3 size 206.47GiB used 206.47GiB path /dev/sdf5
>>
>>
>> btrfs-progs v3.19.1
>>
>>
>>
>> # smartctl -i /dev/sdf
>> smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.14.10-gentoo_s03a_11]
>> (local build)
>> Copyright (C) 2002-14, Bruce Allen, Christian Franke,
>> www.smartmontools.org
>>
>> === START OF INFORMATION SECTION ===
>> Vendor: /7:0:0:0
>> Product:
>> Compliance: SPC-5
>> User Capacity: 600,332,565,813,390,450 bytes [600 PB]
>> Logical block size: 774843950 bytes
>> scsiModePageOffset: response length too short, resp_len=47 offset=50
>> bd_len=46
>> scsiModePageOffset: response length too short, resp_len=47 offset=50
>> bd_len=46
>>>> Terminate command early due to bad response to IEC mode page
>> A mandatory SMART command failed: exiting. To continue, add one or more
>> '-T permissive' options.
>>
>>
>>
>> And btrfs is still running ok so far... I'll be swapping that device at
>> the weekend. (First chance I have for a Sunday shutdown. :-( )
>>
>>
>> Still... For administering btrfs, it is a little disturbing not to be
>> able to remove/delete a device unless that device is both mounted and
>> working...
>>
>> Or is that where the "missing" option comes in?
>>
>>
>>
>> Comments welcomed,
>>
>> Thanks,
>> Martin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-04-01 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 20:59 ERROR: error removing the device '/dev/sdXN' - Inappropriate ioctl for device Martin
2015-03-31 17:37 ` David Sterba
2015-03-31 18:11 ` Martin
2015-04-01 7:06 ` Anand Jain
2015-04-01 10:54 ` Martin
2015-04-01 13:15 ` Anand Jain
2015-04-01 17:28 ` Martin [this message]
2015-04-06 13:32 ` Anand Jain
2015-04-07 11:41 ` Martin
2015-04-13 15:06 ` Anand Jain
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='mfh9rn$2if$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/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).