After reboot my partition table was gone, and neither gpart og
testdisk could recover it. Sad.
Even though the missing partition table right after upgrading
btrfs-tools is a coincidence, I will wait a while before giving btrfs
another chance.
Best of luck with creating a fsck for this promising f
I did a reboot, and now I am trying to recover from a disk with no
partition table. Currently gpart has been running for 30 mins - stupid
me for not printing the partition table.
I did nothing more than executing "make" and "make install" in ./btrs-progs/.
On 22 November 2011 13:56, Jan Schmidt
On 22.11.2011 14:26, René Vangsgaard wrote:
> I got the build working by changing -lpthread to -pthread in the gcc call:
>
> gcc -pthread -g -O0 -o btrfs btrfs.o btrfs_cmds.o scrub.o ctree.o
> disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o
> dir-item.o file-item.o inode-item.o inode
I got the build working by changing -lpthread to -pthread in the gcc call:
gcc -pthread -g -O0 -o btrfs btrfs.o btrfs_cmds.o scrub.o ctree.o
disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o
dir-item.o file-item.o inode-item.o inode-map.o crc32c.o rbtree.o
extent-cache.o extent_io.o vo
On Tue, Nov 22, 2011 at 7:01 AM, René Vangsgaard
wrote:
> I have decided to update progs from git. The instructions on the wiki
> do not really help me out (for example I cannot checkout branch
> "for-chris"). Can anyone tell me what branch (probably integration) to
> use on kernel 3.0.0? Or just
I have decided to update progs from git. The instructions on the wiki
do not really help me out (for example I cannot checkout branch
"for-chris"). Can anyone tell me what branch (probably integration) to
use on kernel 3.0.0? Or just point me to a site with working
instructions.
Thank you, René
O
On Mon, Nov 21, 2011 at 5:29 PM, René Vangsgaard
wrote:
> Thank you for answering.
>
> 2) I get this error when mounting:
> couldn't open because of unsupported option features (8).
> fsck.btrfs: disk-io.c:679: open_ctree_fd: Assertion `!(1)' failed.
You're running an out-of-date version of btrfs
If I change the last column to 0 (aka ignore the warning), my file
system will silently corrupt - is this true?
On 21 November 2011 17:27, Ken D'Ambrosio wrote:
> 1) As of right now, btrfs's fsck is "done when it's done." So don't hold your
> breath, I'm afraid.
>
> 2) What errors do you get on
Thank you for answering.
2) I get this error when mounting:
couldn't open because of unsupported option features (8).
fsck.btrfs: disk-io.c:679: open_ctree_fd: Assertion `!(1)' failed.
My current mount options are
defaults,compress=lzo,subvol=@home
I have tried removing the compress=lzo with no d
1) As of right now, btrfs's fsck is "done when it's done." So don't hold your
breath, I'm afraid.
2) What errors do you get on mount? It may be as simple as changing your fstab
entry such that fsck isn't attempted to be run. (Change the last column to
"0".)
-Ken
On Sat, 19 Nov 2011 14:01:4
10 matches
Mail list logo
