Tomasz Kusmierz posted on Fri, 11 Jul 2014 00:32:33 +0100 as excerpted:
> So it been some time with btrfs, and so far I was very pleased, but
> since I've upgraded to ubuntu from 13.10 to 14.04 problems started to
> occur (YES I know this might be unrelated).
Many points below; might as well star
Hi everybody!
Btrfs filesystem could not be mounted because /dev/sdc1 had unreadable sectors.
It is/was a single filesystem (not raid1 or raid0) over /dev/sda1 and
/dev/sdc1.
I wrote the unreadable sectors with hdparm but filesystem still cannot
be mounted (sectors were too early perhaps).
What
On Fri, 11 Jul 2014 10:38:22 Duncan wrote:
> > I've moved all drives and move those to my main rig which got a nice
> > 16GB of ecc ram, so errors of ram, cpu, controller should be kept
> > theoretically eliminated.
>
> It's worth noting that ECC RAM doesn't necessarily help when it's an in-
> tra
On Fri, 11 Jul 2014 13:42:40 constantine wrote:
> Btrfs filesystem could not be mounted because /dev/sdc1 had unreadable
> sectors. It is/was a single filesystem (not raid1 or raid0) over /dev/sda1
> and /dev/sdc1.
What does "file -s /dev/sda1 /dev/sdc1" report?
--
My Main Blog http://e
On 7/10/14, 8:35 PM, Satoru Takeuchi wrote:
> This is the v3 patch.
>
> ===
> From: Satoru Takeuchi
>
> If "(!IS_ERR(trans) || PTR_ERR(trans) != -ENOSPC))" is false,
> obviously "trans" is -ENOSPC. So we can safely remove the redundant
> "(PTR_ERR(trans) == -ENOSPC)" check.
>
> Signed-off-by:
Thank you very much for your response:
# file -s /dev/sda1 /dev/sdc1
/dev/sda1: BTRFS Filesystem label "partition", sectorsize 4096,
nodesize 4096, leafsize 4096,
UUID=c1eb1aaf-665a-4337-9d04-3c3921aa67e0, 1683870334976/3010310701056
bytes used, 2 devices
/dev/sdc1: data
--
To unsubscribe from thi
On Fri, 11 Jul 2014 21:29:07 constantine wrote:
> Thank you very much for your response:
>
> # file -s /dev/sda1 /dev/sdc1
> /dev/sda1: BTRFS Filesystem label "partition", sectorsize 4096,
> nodesize 4096, leafsize 4096,
> UUID=c1eb1aaf-665a-4337-9d04-3c3921aa67e0, 1683870334976/3010310701056
> by
Given the situation explained below, it appears I can fix my btrfs send
datastream by updating the UUID and CTRANSID of alternate_sv2. Specifically,
Command 1 TLV 1 and 2, or Command 2 TLV 1 and 2. The CRC32 would also be
updated.
This would make incremental btrfs "send" backups markedly more u
