[URGENT] Cannot boot due to BtrFS-Error

Hello Everyone

I’ve got an urgent problem to solve. I just wanted to boot my OpenSuse 12.1 but the process stops on KDM loading the discs.

So I switched to a terminal with CRTL+ALT+F1 and checked my Discs. I could navigate everywhere and out of curiosity I tried to delete a file from my home-folder. This didnt work and got me the impression that there is some kind of write-lock.

After a while the system started to throw out exception-messages in a loop. I cant get the output since it happens on all terminal after some seconds so I cannot look into the logfiles.

The parts I can read say something like this:

Call Trace:
_raw_read_lock+0x1a/0220 (the 0x-part changes)
btrfs_tree_read_lock+=x...
btrfs_read_lock_root_node+0x...
btrfs_search_slot+0x...
btrfs_insert_empty_items+0x
...
extends_write_cache_pages.isra.25.constprop.34+0x...

I need to access my system since I do all my programming on Opensuse. So any help is appreciated.
Thanks in advance
Marc

P.S. my system runs on a 64GB SSD

Macro81 wrote:
> I need to access my system since I do all my programming on Opensuse.
> So any help is appreciated.

Boot it from a DVD or a USB stick. Then you’ll be able to examine the
filesystems at your leisure (fsck etc)

Oh, except there’s no fsck for btrfs is there …

But being as it’s your main [programming] machine, you’ll have good
backups … especially if you chose to use a filesystem with no fsck …

Seriously though. Boot it from an external medium and then investigate
the problem. Good luck.

I cannot help much except to tell you to look at this

https://btrfs.wiki.kernel.org/articles/p/r/o/Problem_FAQ_68af.html

http://btrfs.ipv5.de/index.php?title=Restore

if it helps somehow.


PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.4 |
nVidia ION | 3GB Ram

On 01/19/2012 06:06 PM, Macro81 wrote:
> I need to access my system since I do all my programming on Opensuse.

hmmmm…as far as i know btrfs remains an experimental file system not
yet ready for prime time use…

imo you should not put it on a production system…

i do not know how to fix your btrfs problem but you are very welcome to
hang out here and wait for someone to come along and help…while
waiting you can do some reading on other openSUSE user’s experiences
with btrfs:

btrfs “it’s so fragile (IMO FAT is more stable) that it’s not worth
trying yet … not a single tool to recover data” cite:
http://tinyurl.com/bp2tfkq

“So even though I was excited about it … I wouldn’t recommend it yet.
I even discourage until fsck is available. OR You can end up with ugly
kernel error screen during system boot” cite: http://tinyurl.com/dxbftdf

and over 200 more: http://tinyurl.com/8yhkary

i suggest brtfs only be used on sandbox machines with no data you can’t
afford to lose…other folks may have other suggestions…

be sure and log the bug you found, here: http://tinyurl.com/nzhq7j and
eventually all of them will be found and fixed…


DD http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

Thanks for all the quick replies.

When I decided to go for btrfs there were quite some articles that said it is almost ready. Its not a production-machine…I just do my own littel experiments on it but right now there is one important project :wink:

Since I have a separate home-partition I will go and reinstall the system-partition with ext4 and continue from there. I guess the error came in with a resent kernel-update since it was working very smooth since 12.1 came out.

regards

On 01/19/2012 06:56 PM, Macro81 wrote:
>
> Thanks for all the quick replies.

welcome…

> Since I have a separate home-partition I will go and reinstall the
> system-partition with ext4 and continue from there.

don’t forget to file your bug…


DD http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

After a reinstall the system is up and running again. I kept the filesystem on my home as btrfs and everything works.

I will still backup my files and then update the system. If it fails again after that than there is a problem with a newer kernel than the one the DVD ships with.

If I can get gather some information I will file a bugreport.

On 2012-01-19 20:06, Macro81 wrote:

> I will still backup my files and then update the system. If it fails
> again after that than there is a problem with a newer kernel than the
> one the DVD ships with.

Or the update process failed to umount properly the partition on reboot. I
see it happening on stable filesystem often, which simply fsck and continue
with life.

> If I can get gather some information I will file a bugreport.

Make photos and send them.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)