Alexander Skwar <alexanders.mailinglists+nospam <at> gmail.com> writes: > > Hi > > On Mon, Jun 17, 2013 at 11:43 PM, Alexander Skwar > <alexanders.mailinglists+nospam <at> gmail.com> wrote: > > Hello Josef > > > > On Mon, Jun 17, 2013 at 11:21 PM, Josef Bacik <jbacik <at> fusionio.com> wrote: > > > >> Pull down my tree > >> > >> git://github.com/josefbacik/btrfs-progs.git > >> > >> and build and run the fsck in there and see if it's a bit more friendly. > > > > I just gave it a try, but wasn't successful, it seems… Kernel still > > crashes. > > Maybe checkout the screenphotos at http://goo.gl/DWkRH or > > http://imgur.com/a/00pTx > > Any other ideas, about what I might be able to do, to > revive my btrfs filesystem? > I had the very same problem some days ago. I have not yet found out how to fix the broken btrfs filesystem. However, I have been able to recover all my files from the filesystem and copy them to a brand new ext4 filesystem, that I am using now. To recover files from the broken btrfs filesystem, use the program "btrfs- restore". For example, if the filesystem is on "/dev/sda1" and you want your files to be copied to the directory "/backup", then: $ btrfs-restore /dev/sda1 /backup At the end, all your files should be found at the directory "/backup". If you wish, you can recreate the filesystem on "/dev/sda1" (using mkfs.btrfs or mkfs.ext4) and copy the files back to there. Rodrigo. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
