Hello,
I have a hard drive that is about a year old with some pending sectors
on it. I'd like to RMA this drive out of an abundance of caution.
Doing so requires me removing it from my raid10 array. However I am
unable to do so as it eventually errors out by saying there is no
space left on the de
30.09.2017 14:57, Goffredo Baroncelli пишет:
> (please ignore my previous email, because I wrote somewhere "top id" instead
> of "top level")
> Hi All,
>
> I am trying to figure out which means "top level" in the output of "btrfs sub
> list"
>
>
Digging in git history - "top level" originally
tree: https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
new-kill-btree-inode
head: 5dfd4a0012c1253260da07bee3fa3d4c13aac616
commit: acb56905bda3591b3c0515ebc745340fc20f18da [2/27] Btrfs: rework
outstanding_extents
config: x86_64-randconfig-b0-10011450 (attached as .config)
Adam Bahe posted on Sun, 01 Oct 2017 02:48:19 -0500 as excerpted:
> Hello,
Hi, Just a user and list regular here, not a dev, but perhaps some of
this will be of help.
> I have a hard drive that is about a year old with some pending sectors
> on it. I'd like to RMA this drive out of an abundance
On 2017/10/01 3:17, Holger Hoffstätte wrote:
> On 09/30/17 19:56, Holger Hoffstätte wrote:
>> shell hackery as alternative. Anyway, I was sure that at the time the
>> other letters sounded even worse/were taken, but that may just have been
>> in my head. ;-)
>>
>> I just rechecked and -S is still
This patch changes "subvol set-default" to also accept the subvolume path
for convenience.
This is the one of the issue on github:
https://github.com/kdave/btrfs-progs/issues/35
If there are two args, they are assumed as subvol id and path to the fs
(the same as current behavior), and if there is
