I have upgraded to 3.1 rc8.
I created a new subvolume for /home, copied the files there from the old
subvolume and deleted the old subvolume. It looks like the space has been
reclaimed fine.
Though when doing btrfsck I am still getting the same error
failed to find block number 150121762816
--
Hi,
On Mon, Oct 10, 2011 at 02:14:26AM +, dima wrote:
Somehow my subvolume with /home got corrupted. When I booted the machine this
morning (after perfectly normal shutdown) it gave me a bunch of kernel errors.
That's very strange, if it was a pefrectly normal shutdown, I don't see
a way
Thanks David,
The last shutdown was clean, but I had to powercycle several times this month.
I am also mounting a swapfile via loop device, so maybe this also adds up to
instability.
The corrupt file is a firefox source file
(mozilla-central/js/src/tests/e4x/XML/13.4.4.40.js). Interesting thing
On Mon, Oct 10, 2011 at 11:03:34AM +, dima wrote:
The last shutdown was clean, but I had to powercycle several times this month.
I am also mounting a swapfile via loop device, so maybe this also adds up to
instability.
The corrupt file is a firefox source file
Oh, I see. The fix is not in 3.0.x but on the master branch. I will need the
latest 3.1 RC.
I will try this.
Thanks David
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at
David Sterba wrote:
Then I could mount the /home subvolume.
I also found the corrupted file
? -? ? ? ??? 13.4.4.40.js
Chromium cache? Somebody recently reported a problem there. I wonder
what this browser does to the filesystem ... :)
If you meant me by
Hello,
Somehow my subvolume with /home got corrupted. When I booted the machine this
morning (after perfectly normal shutdown) it gave me a bunch of kernel errors. I
found out that if I comment out my /home entry in fstab, it would boot ok. So
the / is not corrupted. I then booted from the live
