Depending on how important the data is, wanted to throw out the most
prudent first step is to get another set of drives equal to or bigger
than the ones of the bad volume, and image them using dd one by one as
block devices. That gives you an undo button if recovery attempts go
wrong. Always the
Hi, if anyone is able to help with a rather large (34TB of data on it)
BTRFS RAID 6 I would be very grateful (pastebins below) - at this
point I am only interested in recovery since I am obviously switching
to RAID 1 once/if I get my data back.
Many thanks in advance
Chris
Linux rockstor
05.08.2016 02:32, Peter Holm пишет:
> 'btrfs subvolumee show' gives no path to btrfs system root (volid=5)
> when snapshot is in the folder of subvolume.
>
> Step to reproduce.
> 1.btrfs subvolume create xyz
> 2.btrfs subvolume snapshot xyz xyz/xyz
> 3.btrfs subvolume snapshot /xyz
This last
You are right. Typing error. Sorry.
Here is from my bash_history.
1 btrfs su create is-this-a-bug
*2 btrfs su snap is-this-a-bug is-this-a-bug
*3 btrfs su snap is-this-a-bug /mnt/btrfs/sdc16-svid-5/
*2.When snapshot is created with the same name as subvolume, then it
by default creates in the
Thanks Qu,
This patch set fixes all the reported problems. However, I have some
minor issues with coding style.
On 08/04/2016 09:29 PM, Qu Wenruo wrote:
> Refactor btrfs_qgroup_insert_dirty_extent() function, to two functions:
> 1. _btrfs_qgroup_insert_dirty_extent()
>Almost the same with
Hello,
What is the safest way to migrate an existing raid 5/6 setup, to say raid 10?
Will simply running `btrfs filesystem balance start -dconvert=10
-mconvert=10` work or is it sensitive to the parity calculation issue?
Can I `btrfs device delete` some of the drives, format them and copy
over
On Sat, Aug 06, 2016 at 06:11:58PM +0300, Ivan Sizov wrote:
> Is there a way to know when the root tree or generation was created?
> btrfs-find-root doesn't have such option.
In UTC (or similar wall-clock-like units)? Not easily.
I think you'd have to do something like look at the
Is there a way to know when the root tree or generation was created?
btrfs-find-root doesn't have such option.
--
Ivan Sizov (SIvan)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
tried to send this but forgot to set Gmail's Plaintext Mode, so it bounced back.
meanwhile I created this bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=151621
--
Hello.
During unmounting(umount command, umount2 syscall), I've noticed that it
takes a few seconds(sometimes up to 127
I accidentally posted this to Andrei Borzenkov
I repost to the list with the first 3 lines added from what was earlier sent.
Regarding to my manual for btrfs-subvolume dated 01/19/2016 it says.
"If only is given, the subvolume will be named the basename of
. "
So 'btrfs su snap is a shortcut
Thanks Qu,
This patch set fixes all the reported problems. However, I have some
minor issues with coding style.
On 08/04/2016 09:29 PM, Qu Wenruo wrote:
> Refactor btrfs_qgroup_insert_dirty_extent() function, to two functions:
> 1. _btrfs_qgroup_insert_dirty_extent()
>Almost the same with
06.08.2016 11:00, Peter Holm пишет:
> You are right. Typing error. Sorry.
> Here is from my bash_history.
>
> 1 btrfs su create is-this-a-bug
> *2 btrfs su snap is-this-a-bug is-this-a-bug
> *3 btrfs su snap is-this-a-bug /mnt/btrfs/sdc16-svid-5/
>
As I said, in my case it fails with "File
12 matches
Mail list logo
