Re: Filesystem Corruption

2018-12-03 Thread remi
On Mon, Dec 3, 2018, at 4:31 AM, Stefan Malte Schumacher wrote: > I have noticed an unusual amount of crc-errors in downloaded rars, > beginning about a week ago. But lets start with the preliminaries. I > am using Debian Stretch. > Kernel: Linux mars 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4

Re: Filesystem Corruption

2018-12-03 Thread Qu Wenruo
On 2018/12/3 下午5:31, Stefan Malte Schumacher wrote: > Hello, > > I have noticed an unusual amount of crc-errors in downloaded rars, > beginning about a week ago. But lets start with the preliminaries. I > am using Debian Stretch. > Kernel: Linux mars 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4

Re: Filesystem corruption?

2018-10-22 Thread Qu Wenruo
On 2018/10/23 上午4:02, Gervais, Francois wrote: > Hi, > > I think I lost power on my btrfs disk and it looks like it is now in an > unfunctional state. What does the word "unfunctional" mean? Unable to mount? Or what else? > > Any idea how I could debug that issue? > > Here is what I have:

Re: filesystem corruption

2014-11-04 Thread Duncan
Zygo Blaxell posted on Mon, 03 Nov 2014 23:31:45 -0500 as excerpted: On Mon, Nov 03, 2014 at 10:11:18AM -0700, Chris Murphy wrote: On Nov 2, 2014, at 8:43 PM, Zygo Blaxell zblax...@furryterror.org wrote: btrfs seems to assume the data is correct on both disks (the generation numbers and

Re: filesystem corruption

2014-11-04 Thread Chris Murphy
On Nov 3, 2014, at 9:31 PM, Zygo Blaxell zblax...@furryterror.org wrote: On Mon, Nov 03, 2014 at 10:11:18AM -0700, Chris Murphy wrote: On Nov 2, 2014, at 8:43 PM, Zygo Blaxell zblax...@furryterror.org wrote: btrfs seems to assume the data is correct on both disks (the generation numbers

Re: filesystem corruption

2014-11-04 Thread Duncan
Chris Murphy posted on Tue, 04 Nov 2014 11:28:39 -0700 as excerpted: It needs to be more than a sequential number. If one of the disks disappears we need to record this fact on the surviving disks, and also cope with _both_ disks claiming to be the surviving one. I agree this is also a

Re: filesystem corruption

2014-11-04 Thread Robert White
On 11/04/2014 10:28 AM, Chris Murphy wrote: On Nov 3, 2014, at 9:31 PM, Zygo Blaxell zblax...@furryterror.org wrote: Now we have two disks with equal generation numbers. Generations 6..9 on sda are not the same as generations 6..9 on sdb, so if we mix the two disks' metadata we get bad

Re: filesystem corruption

2014-11-04 Thread Zygo Blaxell
On Tue, Nov 04, 2014 at 11:28:39AM -0700, Chris Murphy wrote: On Nov 3, 2014, at 9:31 PM, Zygo Blaxell zblax...@furryterror.org wrote: It needs to be more than a sequential number. If one of the disks disappears we need to record this fact on the surviving disks, and also cope with _both_

Re: filesystem corruption

2014-11-03 Thread Chris Murphy
On Nov 2, 2014, at 8:43 PM, Zygo Blaxell zblax...@furryterror.org wrote: On Sun, Nov 02, 2014 at 02:57:22PM -0700, Chris Murphy wrote: For example if I have a two device Btrfs raid1 for both data and metadata, and one device is removed and I mount -o degraded,rw one of them and make some

Re: filesystem corruption

2014-11-03 Thread Zygo Blaxell
On Mon, Nov 03, 2014 at 10:11:18AM -0700, Chris Murphy wrote: On Nov 2, 2014, at 8:43 PM, Zygo Blaxell zblax...@furryterror.org wrote: btrfs seems to assume the data is correct on both disks (the generation numbers and checksums are OK) but gets confused by equally plausible but different

Re: filesystem corruption

2014-11-02 Thread Chris Murphy
On Nov 1, 2014, at 10:49 PM, Robert White rwh...@pobox.com wrote: On 10/31/2014 10:34 AM, Tobias Holst wrote: I am now using another system with kernel 3.17.2 and btrfs-tools 3.17 and inserted one of the two HDDs of my btrfs-RAID1 to it. I can't add the second one as there are only two slots

Re: filesystem corruption

2014-11-02 Thread Tobias Holst
Thank you for your reply. I'll answer in-line. 2014-11-02 5:49 GMT+01:00 Robert White rwh...@pobox.com: On 10/31/2014 10:34 AM, Tobias Holst wrote: I am now using another system with kernel 3.17.2 and btrfs-tools 3.17 and inserted one of the two HDDs of my btrfs-RAID1 to it. I can't add

Re: filesystem corruption

2014-11-02 Thread Zygo Blaxell
On Sun, Nov 02, 2014 at 02:57:22PM -0700, Chris Murphy wrote: On Nov 1, 2014, at 10:49 PM, Robert White rwh...@pobox.com wrote: On 10/31/2014 10:34 AM, Tobias Holst wrote: I am now using another system with kernel 3.17.2 and btrfs-tools 3.17 and inserted one of the two HDDs of my

Re: filesystem corruption

2014-11-02 Thread Robert White
On 11/02/2014 06:55 PM, Tobias Holst wrote: But I can't do a balance anymore? root@t-mon:~# btrfs balance start /dev/sda1 ERROR: can't access '/dev/sda1' Balance takes place on a mounted filesystem not a native block device. So... mount -t btrfs /dev/sda1 /some/path/somewhere btrfs balance

Re: filesystem corruption

2014-11-01 Thread Robert White
On 10/31/2014 10:34 AM, Tobias Holst wrote: I am now using another system with kernel 3.17.2 and btrfs-tools 3.17 and inserted one of the two HDDs of my btrfs-RAID1 to it. I can't add the second one as there are only two slots in that server. This is what I got: tobby@ubuntu: sudo btrfs

Re: filesystem corruption

2014-10-31 Thread Tobias Holst
I am now using another system with kernel 3.17.2 and btrfs-tools 3.17 and inserted one of the two HDDs of my btrfs-RAID1 to it. I can't add the second one as there are only two slots in that server. This is what I got: tobby@ubuntu: sudo btrfs check /dev/sdb1 warning, device 2 is missing

Re: filesystem corruption

2014-10-30 Thread Tobias Holst
Addition: I found some posts here about a general file system corruption in 3.17 and 3.17.1 - is this the cause? Additionally I am using ro-snapshots - maybe this is the cause, too? Anyway: Can I fix that or do I have to reinstall? Haven't touched the filesystem, just did a scrub (found 0

Re: filesystem corruption

2014-10-30 Thread Rich Freeman
On Thu, Oct 30, 2014 at 9:02 PM, Tobias Holst to...@tobby.eu wrote: Addition: I found some posts here about a general file system corruption in 3.17 and 3.17.1 - is this the cause? Additionally I am using ro-snapshots - maybe this is the cause, too? Anyway: Can I fix that or do I have to