Hi,
Am 2013-09-20 06:49, schrieb Jérôme Poulin:
Did you make sure you aren't working with a dead SSD?
The SSDs are working quite fine. I was worried about that too, but
since I managed to get raw disk images using `dd` I was pretty sure they
were alright. In fact I reinstalled Debian on the
Hello Jogi,
I'm not sure what's causing the free error, I'll keep looking.
Have you tried running restore on your home subvolume yet? By default
restore only works on the default subvolume which in your case is /
The following command will try to restore your /home subvolume
btrfs restore -i -r
Hello Frank,
Am 2013-09-19 18:18, schrieb Frank Holton:
I'm not sure what's causing the free error, I'll keep looking.
So am I :) In fact I would really like to help fix the tool. I hope I
can provide some suggestions for fixes, but I'm having my trouble with
the code ;)
All I can tell so
On Mon, Sep 16, 2013 at 6:48 AM, Jogi Hofmüller j...@mur.at wrote:
After btrfs-zero-log the device
was still not mountable. Mount attempts fail with i/o erros now.
...
All this is happening on an Asus Zen book UX32V with two 128GB SSDs.
Did you make sure you aren't working with a dead SSD?
Hi Clemens, all,
Am 2013-09-17 20:53, schrieb Clemens Eisserer:
a. comment out the free()-calls which led to crashes
Uh, well, I did not want to go that far ;) I'm certainly not the
greatest programmer around, but not freeing allocated memory seems kind
of drastic.
Anyway, I checked out a
Dear all,
After trying all the suggested options from
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/27999
I still get no mountable file system :(
Trying to mount I get
mount -oro,recovery,compress=lzo /dev/sda3 /rootfs
[ 906.835314] btrfs: enabling auto recovery
[ 906.836977]
Jogi Hofmüller wrote (ao):
I am limited to working with the tools the Debian initramfs
provides. This means kernel 3.10.2 (Debian 3.10.7-1) and
btrfs-tools 0.19+20130705-1. The latter seems to be up to date
with git although `btrfs version` says v0.20 rc1. All this is
happening on an Asus
Hi,
Am 2013-09-17 13:18, schrieb Sander:
Jogi Hofmüller wrote (ao):
I am fresh out of ideas at the moment, so if anyone has a suggestion
I am willing to try.
Did you try btrfs chunk-recover ?
Yes, did so. It stopped with an error. I will send the error message
later since it resides
Hi,
Am 2013-09-17 14:24, schrieb Jogi Hofmüller:
Yes, did so. It stopped with an error. I will send the error
message later since it resides on a different machine that I cannot
access from where I am now.
This is the promised output of
btrfs chunk-recover -y -v /dev/sda3
[ 1090.896935]
Hi Jogi,
When I tried to recovered a broken btrfs-parition, I encountered the
same errors you did - btrfs restore seems to be a bit broken.
What helped was to:
a. comment out the free()-calls which led to crashes
b. re-run btrfs restore to account for the crashes which happen
elsewhere,
Dear all,
Yesterday the rootfs on my laptop crashed. So far all attempts to fix
it have failed; hence I am looking for some help (if possible).
I was creating a copy of a virtual machine (kvm) on my laptop and
started modifying the machine from the inside (installing new packages),
when the
11 matches
Mail list logo
