From: Goffredo Baroncelli <kreijack@inwind.it>
To: Lester B <b.lester011+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs resize problem after device add/delete
Date: Sat, 09 Nov 2013 11:55:27 +0100 [thread overview]
Message-ID: <527E149F.3090001@inwind.it> (raw)
In-Reply-To: <CAOeUAF_80gVV-uDAw1Z_kQreOze-mW6uUCSheM_eBb_TYq_fuw@mail.gmail.com>
On 2013-11-08 23:09, Lester B wrote:
> I create a new btrfs filesystem and then add a new device and delete
> the original device. When I run 'btrfs filesystem show', the total
> device is two and there is an error that some devices are missing.
See my answer below.
>
> I also tried to resize the filesystem but didn't work. Resizing
> without device id have an error that there is no such device. When the
> device id is explicitly pass, an error 'invalid argument' is
> displayed.
We need more info:
- what is the output of "btrfs filesystem df <path>"
- which is a raid level involved (RAID1/DUP/...), if any ?
- which command you perform to shrink/enlarge the partition and which
one to resize the filesystem (these are two separate steps) ?
>
> I tried to unmount and then remount and the first problem disappeared
> while the second one didn't.
Unfortunately "btrfs filesystem show" read the data from the disk, that
time to time is outdated.
>
> 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64 GNU/Linux
>
> Btrfs v0.20-rc1-358-g194aa4a-dirty
> --
> 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
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
prev parent reply other threads:[~2013-11-09 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 22:09 Btrfs resize problem after device add/delete Lester B
2013-11-09 10:55 ` Goffredo Baroncelli [this message]
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=527E149F.3090001@inwind.it \
--to=kreijack@inwind.it \
--cc=b.lester011+btrfs@gmail.com \
--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.