search for: problem_faq

Hello all, I recently had a power failure and can no longer mount my /home directory. The harddrive has two BTRFS partitions: sda7(/) and sda8(/home). The / partition loads up just fine, but /home does not. I''ve tried btrfsck as shown below and I''ve included dmesg pertaining to btrfs. This is on ArchLinux and the software versions are as follows: btrfs-progs-unstable

...est: - I started Ubuntu on a live CD - before invoking the btrfsctl command I invoked apt-get update. I have googled but have not found anything that seems to help me. I have searched for "resize" on the following pages but have not find anything: https://btrfs.wiki.kernel.org/index.php/Problem_FAQ https://btrfs.wiki.kernel.org/index.php/Gotchas Thanks, Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

I have the attached error from trying to mount btrfs on external hard drive. The F.S. was my primary system, then I dd''d it to an external and reinstalled Fedora. I tried to follow https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Filesystem_can.27t_be_mounted_by_label. I used "# btrfs device scan --all-devices" before attempting to mount.   What should I do? Appreciatively, Gatlin. P.S. This file system is very important to me becasue it has a large collection of songs.

Hello! Long time ago I created btrfs on /dev/sda After some changes btrfs moved to /dev/sda1 (well, to md, and sda1 is part of md). As result, <btrfs fi show> show me 2 filesystems: new one and old one. Probably I need to do some cleaning. Can someone tell me what to do. fdisk -u -c -l /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 81 heads, 63 sectors/track, 765633 cylinders,

I set the C (NOCOW) and z (Not_Compressed) flags on a folder but the extent counts of files contained there keep increasing. Said files are large and frequently modified but not changing in size. This does not happen when the filesystem is mounted with nodatacow. I''m using this as a workaround since subvolumes can''t be mounted with different options simultaneously. ie. one with

...-zero-log business, which in the end fixed my problem, should not be a routine recovery method, especially because the ooops you get on your screen doesn''t have the proper info that tells you that it''s actually the right bug as described on https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21 Could mainline kernels be fixed not to oops so badly and in a hard to debug way when this problem which happens too often (at least for me), is hit? If that helps, here''s what I got after the fact when trying to mount the brok...

I''ve filed this bug under util-linux, because I think wipefs isn''t deleting all btrfs metadata it could. But ultimately it appears to be a btrfs bug because nothing else sees the stale volume. https://bugzilla.redhat.com/show_bug.cgi?id=889888#c15 btrfs-progs-0.20.rc1.20121017git92d9eec-1.fc18.x86_64 e2fs-progs-1.42.5-1.fc18.x86_64 kernel 3.7.1-2 Brand new 80GB virtual disk,

hi All, I''m new on the list. System: Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring Linux ctu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux The symptom is the same with Saucy 3.9 kernel. ii btrfs-tools 0.20~git20130524~650e656-0daily13~raring1 amd64 Checksumming Copy on