All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 31 Mar 2015 19:11:47 +0100	[thread overview]
Message-ID: <mfeo14$sib$1@ger.gmane.org> (raw)
In-Reply-To: <20150331173756.GF6821@twin.jikos.cz>

On 31/03/15 18:37, David Sterba wrote:
> On Mon, Mar 30, 2015 at 09:59:05PM +0100, Martin wrote:
>> btrfs device delete /dev/sdf5 /mnt/data2
>>
>> ERROR: error removing the device '/dev/sdf5' - Inappropriate ioctl for
>> device
> 
> Strange, that would mean that the ioctl number is not handled at all. I
> haven't found any change in device delete on the userspace side. This
> would mean that /mnt/data2 is not mounted. Did you try to do lazy
> unmount?

Nope, that filesystem is still mounted and in use, but still a very good
deduction...

Trying smartmonctl just now on that drive (/dev/sdf) gives errors
suggesting that the drive is no longer responding at all :-(

There is also a steady repeat of:

kernel: sd 7:0:0:0: [sdf] CDB:
kernel: cdb[0]=0x2a: 2a 00 04 02 45 80 00 00 08 00
kernel: sd 7:0:0:0: [sdf] Unhandled error code
kernel: sd 7:0:0:0: [sdf]
kernel: Result: hostbyte=0x04 driverbyte=0x00

(Must watch that lot doesn't fill the log.)


Should I try a:

btrfs device delete missing /mnt/data2

or do I need to unmount or remount first?


... And the system is live and not to be rebooted if at all possible
until the weekend...

Thanks,
Martin


  reply	other threads:[~2015-03-31 18:12 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 [this message]
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
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='mfeo14$sib$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 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.