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, 07 Apr 2015 12:41:21 +0100 [thread overview]
Message-ID: <mg0fp1$ep4$1@ger.gmane.org> (raw)
In-Reply-To: <55228ADB.3000404@oracle.com>
On 06/04/15 14:32, Anand Jain wrote:
> btrfs fi show -d
That gives:
# btrfs fi show -d
warning, device 3 is missing
warning devid 3 not found already
warning, device 3 is missing
warning devid 3 not found already
Label: 'btrfs_root' uuid: 92452e9a-2775-45c4-922c-f01b2afd51c2
Total devices 3 FS bytes used 30.94GiB
devid 1 size 24.00GiB used 24.00GiB path /dev/sda4
devid 2 size 24.00GiB used 24.00GiB path /dev/sdc4
devid 3 size 24.00GiB used 24.00GiB path /dev/sde4
Label: 'btrfs_data' uuid: d1b96638-be89-4291-8a40-f2f2e1dc5223
Total devices 3 FS bytes used 95.74GiB
devid 1 size 87.24GiB used 86.48GiB path /dev/sda5
devid 2 size 87.24GiB used 87.24GiB path /dev/sdc5
devid 3 size 87.24GiB used 87.24GiB path /dev/sde5
Label: 'btrfs_root2' uuid: 62603ce8-c333-4ca7-92f7-f8bdd712ab37
Total devices 3 FS bytes used 151.60MiB
devid 1 size 24.00GiB used 24.00GiB path /dev/sdb4
devid 2 size 24.00GiB used 24.00GiB path /dev/sdd4
*** Some devices missing
Label: 'btrfs_data2' uuid: 3aaee716-b98b-4c86-ba5a-53456994f152
Total devices 3 FS bytes used 159.34GiB
devid 1 size 206.47GiB used 206.02GiB path /dev/sdb5
devid 2 size 206.47GiB used 206.47GiB path /dev/sdd5
*** Some devices missing
btrfs-progs v3.19.1
And without the "-d":
# btrfs fi show
Label: 'btrfs_root' uuid: 92452e9a-2775-45c4-922c-f01b2afd51c2
Total devices 3 FS bytes used 30.94GiB
devid 1 size 24.00GiB used 24.00GiB path /dev/sda4
devid 2 size 24.00GiB used 24.00GiB path /dev/sdc4
devid 3 size 24.00GiB used 24.00GiB path /dev/sde4
Label: 'btrfs_data' uuid: d1b96638-be89-4291-8a40-f2f2e1dc5223
Total devices 3 FS bytes used 95.74GiB
devid 1 size 87.24GiB used 86.48GiB path /dev/sda5
devid 2 size 87.24GiB used 87.24GiB path /dev/sdc5
devid 3 size 87.24GiB used 87.24GiB path /dev/sde5
Label: 'btrfs_root2' uuid: 62603ce8-c333-4ca7-92f7-f8bdd712ab37
Total devices 3 FS bytes used 151.60MiB
devid 1 size 24.00GiB used 24.00GiB path /dev/sdb4
devid 2 size 24.00GiB used 24.00GiB path /dev/sdd4
devid 3 size 24.00GiB used 24.00GiB path /dev/sdf4
Label: 'btrfs_data2' uuid: 3aaee716-b98b-4c86-ba5a-53456994f152
Total devices 3 FS bytes used 159.34GiB
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
Interestingly, all the log messages about /dev/sdf are now no longer
being repeated.
(And nope, not had a chance to swap that disk yet!)
Hence, should I do a "btrfs device delete missing /mnt/data2"?
Cheers,
Martin
next prev parent reply other threads:[~2015-04-07 11:41 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
2015-04-06 13:32 ` Anand Jain
2015-04-07 11:41 ` Martin [this message]
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='mg0fp1$ep4$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).