OK, I see. Maybe there is even more damaged...
Now I finished my second backup of the important data and just
killed this damaged raid. I created a new one and now I am restoring
my data. Let's hope it will last longer this time :)
Regards,
Tobias
2015-02-15 4:30 GMT+01:00 Liu Bo
On Fri, Feb 13, 2015 at 10:54:22PM +0100, Tobias Holst wrote:
It's me again. I just found out why my system crashed during the back up.
I don't know what it means, but maybe it helps you?
The warning means somehow checksum becomes inconsistent with file extents, but
no clear clues about the
On Fri, Feb 13, 2015 at 12:22:16AM +0100, Tobias Holst wrote:
Hi
I don't remember the exact mkfs.btrfs options anymore but
ls /sys/fs/btrfs/[UUID]/features/
shows the following output:
big_metadata compress_lzo extended_iref mixed_backref raid56
Well... mkfs.btrfs can specify a '-m'
2015-02-13 9:06 GMT+01:00 Liu Bo bo.li@oracle.com:
On Fri, Feb 13, 2015 at 12:22:16AM +0100, Tobias Holst wrote:
Hi
I don't remember the exact mkfs.btrfs options anymore but
ls /sys/fs/btrfs/[UUID]/features/
shows the following output:
big_metadata compress_lzo extended_iref
It's me again. I just found out why my system crashed during the back up.
I don't know what it means, but maybe it helps you?
WARNING: CPU: 7 PID: 22878 at
/home/kernel/COD/linux/fs/btrfs/extent_io.c:5203
read_extent_buffer+0xe3/0x120 [btrfs]()
Modules linked in: raid0(E) ufs(E) qnx4(E)
Hi
I don't remember the exact mkfs.btrfs options anymore but
ls /sys/fs/btrfs/[UUID]/features/
shows the following output:
big_metadata compress_lzo extended_iref mixed_backref raid56
I also tested my device with a short
hdparm -tT /dev/dm5
and got
/dev/mapper/sdc_crypt:
Timing cached
Ed Tomlinson e...@aei.ca schrieb:
On Tuesday, February 10, 2015 2:17:43 AM EST, Kai Krakow wrote:
Tobias Holst to...@tobby.eu schrieb:
and btrfs scrub status /[device] gives me the following output:
scrub status for [UUID]
scrub started at Mon Feb 9 18:16:38 2015 and was aborted after 2008
Hmm, it looks like it is getting worse... Here are some parts of my
syslog, including two crashed btrfs-threads:
So I am still getting many of these:
BTRFS (device dm-5): parent transid verify failed on 25033166798848 wanted
108976 found 108958
BTRFS warning (device dm-5): page private not
2015-02-10 8:17 GMT+01:00 Kai Krakow hurikha...@gmail.com:
Tobias Holst to...@tobby.eu schrieb:
and btrfs scrub status /[device] gives me the following output:
scrub status for [UUID]
scrub started at Mon Feb 9 18:16:38 2015 and was aborted after 2008
seconds total bytes scrubbed: 113.04GiB
Tobias Holst posted on Mon, 09 Feb 2015 23:45:21 +0100 as excerpted:
So a short summary:
- btrfs raid6 on 3.19.0 with btrfs-progs 3.19-rc2
- does not mount at boot up, open_ctree failed (disk 3)
- mounts successfully after bootup
- randomly checksum verify failed (disk 5)
- balance and
Hi
I'm having some trouble with my six-drives btrfs raid6 (each drive
encrypted with LUKS). At first: Yes, I do have backups, but it may
take at least days, maybe weeks or even some month to restore
everything from the (offside) backups. So it is not essential to
recover the data, but would be
11 matches
Mail list logo
