Kai Krakow posted on Sun, 03 Apr 2016 06:02:02 +0200 as excerpted:
> No, other files are affected, too. And it looks like those files are
> easily affected even when removed and recreated from whatever backup
> source.
I've seen you say that several times now, I think. But none of those
times h
Am Sat, 2 Apr 2016 18:14:17 -0600
schrieb Chris Murphy :
> On Sat, Apr 2, 2016 at 2:16 PM, Kai Krakow
> wrote:
>
> > I'll go checking the RAM for problems - tho that would be the first
> > time in twenty years that a RAM module hadn't errors from the
> > beginning. Well, you'll never know. But I
On 04/03/2016 12:29 AM, Ivan P wrote:
It's about 800Mb, I think I could upload that.
I ran it with the -s parameter, is that enough to remove all personal
info from the image?
Also, I had to run it with -w because otherwise it died on the same
corrupt node.
You can also use -c9 to further co
On Sat, Apr 2, 2016 at 2:16 PM, Kai Krakow wrote:
> I'll go checking the RAM for problems - tho that would be the first
> time in twenty years that a RAM module hadn't errors from the
> beginning. Well, you'll never know. But I expect no error since usually
> this would mean all sorts of differen
Am Sat, 2 Apr 2016 19:17:55 +0200
schrieb Henk Slager :
> On Sat, Apr 2, 2016 at 11:00 AM, Kai Krakow
> wrote:
> > Am Fri, 1 Apr 2016 01:27:21 +0200
> > schrieb Henk Slager :
> >
> >> It is not clear to me what 'Gentoo patch-set r1' is and does. So
> >> just boot a vanilla v4.5 kernel from kern
On Thu, Mar 31, 2016 at 11:57 PM, Marc Haber
wrote:
> On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote:
>> Am Thu, 31 Mar 2016 23:00:04 +0200
>> schrieb Marc Haber :
>> > I find it somewhere between funny and disturbing that the first call
>> > of btrfs check made my kernel log the follo
On 2 April 2016 at 20:31, Kai Krakow wrote:
> Am Sat, 2 Apr 2016 11:44:32 +0200
> schrieb Marc Haber :
>
>> On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote:
>> > Am Fri, 1 Apr 2016 07:57:25 +0200
>> > schrieb Marc Haber :
>> > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote
Am Sat, 2 Apr 2016 11:44:32 +0200
schrieb Marc Haber :
> On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote:
> > Am Fri, 1 Apr 2016 07:57:25 +0200
> > schrieb Marc Haber :
> > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote:
> [...]
> [...]
> [...]
> > >
> > > I
On Sat, Apr 2, 2016 at 11:00 AM, Kai Krakow wrote:
> Am Fri, 1 Apr 2016 01:27:21 +0200
> schrieb Henk Slager :
>
>> It is not clear to me what 'Gentoo patch-set r1' is and does. So just
>> boot a vanilla v4.5 kernel from kernel.org and see if you get csum
>> errors in dmesg.
>
> It is the gentoo p
It's about 800Mb, I think I could upload that.
I ran it with the -s parameter, is that enough to remove all personal
info from the image?
Also, I had to run it with -w because otherwise it died on the same
corrupt node.
On Fri, Apr 1, 2016 at 2:25 AM, Qu Wenruo wrote:
>
>
> Ivan P wrote on 2016/
Hi,
I've got a big BTRFS raid10 set that fails to mount. I'm currently
running "btrfs restore" on the most important stuff, but would
appreciate any ideas on how to fix the FS gracefully.
# btrfs de scan
# mount -o clear_cache,recovery,degraded /dev/sdh1 /mnt/raid/
mount: /dev/sdh1: can't read su
On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote:
> Am Fri, 1 Apr 2016 07:57:25 +0200
> schrieb Marc Haber :
> > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote:
> > > Am Thu, 31 Mar 2016 23:00:04 +0200
> > > schrieb Marc Haber :
> > > > I find it somewhere between funny and
Am Fri, 1 Apr 2016 07:57:25 +0200
schrieb Marc Haber :
> On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote:
> > Am Thu, 31 Mar 2016 23:00:04 +0200
> > schrieb Marc Haber :
> > > I find it somewhere between funny and disturbing that the first
> > > call of btrfs check made my kernel log
Am Fri, 1 Apr 2016 01:27:21 +0200
schrieb Henk Slager :
> It is not clear to me what 'Gentoo patch-set r1' is and does. So just
> boot a vanilla v4.5 kernel from kernel.org and see if you get csum
> errors in dmesg.
It is the gentoo patchset, I don't think anything there relates to
btrfs:
https:/
Am Fri, 1 Apr 2016 09:10:44 +0800
schrieb Qu Wenruo :
> The real problem is, the extent has mismatched reference.
> Normally it can fixed by --init-extent-tree option, but it normally
> means bigger problem, especially it has already caused kernel
> delayed-ref problem.
>
> No to mention the er
Chris Murphy posted on Fri, 01 Apr 2016 23:43:46 -0600 as excerpted:
> On Fri, Apr 1, 2016 at 10:55 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>> Marc Haber posted on Fri, 01 Apr 2016 15:40:29 +0200 as excerpted:
>
>>> [4/502]mh@swivel:~$ sudo btrfs fi usage / Overall:
>>> Device size:
16 matches
Mail list logo
