Christian Rene Thelen posted on Sun, 13 Aug 2017 19:12:48 +0200 as
excerpted:
> I have formated an encrypted disk, containing a LVM with a btrfs system.
>
> All superblocks appear to be destroyed; the btrfs-progs tools can't find
> the root tree anymore and scalpel, binwalk, foremost & co return
On Sun, Aug 13, 2017 at 9:31 AM, Geert Uytterhoeven
wrote:
> On Fri, Aug 4, 2017 at 10:19 PM, Nick Terrell wrote:
>> --- a/fs/squashfs/decompressor.c
>> +++ b/fs/squashfs/decompressor.c
>> @@ -65,6 +65,12 @@ static const struct squashfs_decompressor
>>
Hi Chris,
Thank you very much for your suggestion.
I didn't remember which steps that I made a mistake and made the mysql had
Received
UUID.
I have done the following and it work as it should be right now.
[root@backuplogC7 mariadb]# btrfs subvolume snapshot mbroken_201708070830
Hi "A L",
Thank you very much for your suggestion. I've got it.
It work properly right now.
what I have done are following.
mv all current mysql and snapshot mysql to mbroken and mbroken_yymmddhhmm
btrfs subvolume snapshot mbroken to mysql (to make it rw subvolume without
Recieve
UUID)
btrfs
Would that be useful to build a BTRFS test machine, which will perform
both software tests (btrfs send | btrfs receive, read/write random
data etc.) and hardware tests, such as abrupt power off test, abruptly
removing a raid-X disk physically, etc.
If it would be useful, what tests should it
On Sun, Aug 13, 2017 at 8:45 PM, Chris Murphy wrote:
> Further, the error detection of corrupt reconstruction is why I say
> Btrfs is not subject *in practice* to the write hole problem. [2]
>
> [1]
> I haven't tested the raid6 normal read case where a stripe contains
>
From: siranee...@tpc.co.th -- Sent: 2017-08-13 - 16:00
> Hi "A L",
>
> As your suggestion. Does it mean I have to make all my current subvolumes to
> clear
> "Receive UUID" and send them with full snapshots?
You need to clear all subvolumes with 'Received UUID' in order to use
On Sun, Aug 13, 2017 at 4:52 AM, wrote:
> Hi "A L",
>
> [root@backuplogC7 ~]# btrfs sub show /var/lib/mariadb/mysql
> /var/lib/mariadb/mysql
> Name: mysql
> UUID: 92f319c5-e132-3249-9b13-d39ee77a2b44
> Parent UUID:
On Sun, Aug 13, 2017 at 4:49 AM, wrote:
> [root@backuplogC7 ~]# btrfs send /var/lib/mariadb/mysql_201708090830 | ssh
> 192.168.45.166 btrfs receive /var/lib/mariadb
> At subvol /var/lib/mariadb/mysql_201708090830
> At subvol mysql_201708090830
> [root@backuplogC7 ~]# rsync
On Sun, Aug 13, 2017 at 8:16 AM, Goffredo Baroncelli wrote:
> Hi all,
>
> in the BTRFS wiki, in the status page, in the "line" RAID5/6 it is reported
> that the parity is not checksummed. This was reported several time in the ML
> and also on other site (e.g. phoronix) as a
On Sun, Aug 13, 2017 at 11:12 AM, Christian Rene Thelen wrote:
> I have formated an encrypted disk, containing a LVM with a btrfs system.
>
> All superblocks appear to be destroyed;
This is an unclear description. I don't understand the exact layout of
the storage stack, and what
On Sun, Aug 13, 2017 at 07:12:48PM +0200, Christian Rene Thelen wrote:
> I have formated an encrypted disk, containing a LVM with a btrfs system.
What did you format it as? (i.e. what are the locations of the
damaged blocks?)
> All superblocks appear to be destroyed; the btrfs-progs tools
I have formated an encrypted disk, containing a LVM with a btrfs system.
All superblocks appear to be destroyed; the btrfs-progs tools can't find the
root tree anymore and scalpel, binwalk, foremost & co return only scrap. The
filesystem was on an ssd and mounted with -o compression=lzo.
How
Back in 2014 Ted Tso introduced the lazytime mount option for ext4 and
shortly thereafter a more generic VFS implementation which was then
merged into mainline. His early patches included support for Btrfs but
those changes were removed prior to the feature being merged. His
changelog includes
Hi all,
in the BTRFS wiki, in the status page, in the "line" RAID5/6 it is reported
that the parity is not checksummed. This was reported several time in the ML
and also on other site (e.g. phoronix) as a BTRFS defect.
However I was unable to understand it, and I am supposing that this is a
On 08/12/2017 02:12 PM, Hugo Mills wrote:
> On Sat, Aug 12, 2017 at 01:51:46PM +0200, Christoph Anton Mitterer wrote:
>> On Sat, 2017-08-12 at 00:42 -0700, Christoph Hellwig wrote:
[...]
>> good, but csum is not
>
>I don't think this is a particularly good description of
Hi "A L",
As your suggestion. Does it mean I have to make all my current subvolumes to
clear
"Receive UUID" and send them with full snapshots?
>> mysql
>> mysql_201708060830
>> mysql_201708070830
On 8/13/2017 12:52 PM, siranee...@tpc.co.th wrote:
Hi "A L",
[root@backuplogC7 ~]# btrfs sub show /var/lib/mariadb/mysql
/var/lib/mariadb/mysql
Name: mysql
UUID: 92f319c5-e132-3249-9b13-d39ee77a2b44
Parent UUID:-
Hi "A L",
[root@backuplogC7 ~]# btrfs sub show /var/lib/mariadb/mysql
/var/lib/mariadb/mysql
Name: mysql
UUID: 92f319c5-e132-3249-9b13-d39ee77a2b44
Parent UUID:-
Received UUID:
Hi Chris,
Try deleting mysql_201708090830/ snapshot on the destination. And
resend but this time do a full send of that snapshot, don't use -p. I
wonder if a full send, rather than incremental makes a difference.
Follow it up with the rsync command to compare origin and destination.
Yes, It's
On Fri, Aug 4, 2017 at 10:19 PM, Nick Terrell wrote:
> --- a/fs/squashfs/decompressor.c
> +++ b/fs/squashfs/decompressor.c
> @@ -65,6 +65,12 @@ static const struct squashfs_decompressor
> squashfs_zlib_comp_ops = {
> };
> #endif
>
> +#ifndef CONFIG_SQUASHFS_ZSTD
> +static
Have you checked that there is no Received UUID on the source subvolume?
# btrfs sub show volume/mysql/
volume/mysql
Name: mysql
UUID: 8a94524e-a956-c14b-bb8d-d453627f27d5
Parent UUID: -
Received UUID: -
22 matches
Mail list logo