First, my apologies for the broken threads, I had one message where I
updated the subject line, but it got cut in two and sent part of the
headers in the body :(
(operator mistake, sorry)
On Sun, May 11, 2014 at 02:28:23AM +, Duncan wrote:
That's a fair point but I run scrub every day with
On May 10, 2014 10:09 AM, Hugo Mills h...@carfax.org.uk wrote:
As in, Your filesystem got corruption as a result of a bug in some
earlier version. Upgrading to the new version isn't magically going to
make that corruption go away. (Not saying that's what's happened
here, but it's common,
On Fri, May 09, 2014 at 07:54:20PM -0600, Chris Murphy wrote:
However, I have a recent case in VBox guest, with guest additions
built. That cause the kernel to be tainted G because it's an out
of tree kernel module for guest additions. I'm getting a bunch of
Btrfs errors that aren't
On May 10, 2014, at 7:51 AM, Marc MERLIN m...@merlins.org wrote:
Note that in my case, I wasn't trying to run linux inside vbox, just to
start a win7 vm guest on my linux laptop.
Is that a case that also is known to cause problems?
No, the host experiences no issues, although in my case the
Marc MERLIN posted on Fri, 09 May 2014 20:40:26 -0700 as excerpted:
On May 10, 2014 10:09 AM, Hugo Mills h...@carfax.org.uk wrote:
As in, Your filesystem got corruption as a result of a bug in some
earlier version. Upgrading to the new version isn't magically going to
make that corruption
Ok, first for the devs, I found the real trace that happened just before the
system went
read only
My apologies for pasting the bad one first.
I'll wipe/rebuild the FS tonight unless you ask me to wait for one more day
and/or data off it.
Please advise if I should rebuilt with 3.14.3 or
On May 9, 2014, at 4:36 PM, Marc MERLIN m...@merlins.org wrote:
Details:
It looks like my corruption came from there.
I'm still not sure why it's apparently so severe that btrfs recovery cannot
open the FS now.
WARNING: CPU: 6 PID: 555 at fs/btrfs/extent-tree.c:5748
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marc,
On Fri, 9 May 2014 03:36:59 PM Marc MERLIN wrote:
Oh, I missed that.
May 2 14:23:06 legolas kernel: [283268.319035] CPU: 0 PID: 25726 Comm:
watchdog/0 Tainted: GW3.14.0-amd64-i915-preempt-20140216 #2
This is weird because I
On Sat, May 10, 2014 at 10:13:43AM +1000, Chris Samuel wrote:
Right now, I do see:
legolas:~# cat /proc/sys/kernel/tainted
512
IIUC that's an array of bit flags, and that value means you've had a previous
kernel warning at that point according to:
On Fri, May 09, 2014 at 05:42:54PM -0700, Marc MERLIN wrote:
On Sat, May 10, 2014 at 10:13:43AM +1000, Chris Samuel wrote:
Right now, I do see:
legolas:~# cat /proc/sys/kernel/tainted
512
IIUC that's an array of bit flags, and that value means you've had a
previous
kernel
On Fri, May 09, 2014 at 06:00:50PM -0600, Chris Murphy wrote:
Well I'm sorta dense, so I only find a complete dmesg useful because
with storage problems it seems much is due to some other problem
happening earlier.
Life would be so much easier if filesystems didn't store any
persistent
On May 9, 2014, at 7:05 PM, Hugo Mills h...@carfax.org.uk wrote:
On Fri, May 09, 2014 at 05:42:54PM -0700, Marc MERLIN wrote:
On Sat, May 10, 2014 at 10:13:43AM +1000, Chris Samuel wrote:
Right now, I do see:
legolas:~# cat /proc/sys/kernel/tainted
512
IIUC that's an array of bit flags,
Hugo Mills posted on Sat, 10 May 2014 02:09:02 +0100 as excerpted:
Life would be so much easier if filesystems didn't store any
persistent state... :)
The number of people who don't quite get that that's the function
and natural behaviour of a filesystem is... surprising.
As in, Your
13 matches
Mail list logo
