mount errors

mount errors

[René Vangsgaard]

Hi - I have been using btrfs on /home for 2 weeks, and now it mounts
with errors. I know that no fsck is available yet. I ignore the error
and it still works, for now. Can I do anything to help you debug this
problem with btrfs?
Any news on fsck for btrfs?

I am running Ubuntu 11.10.
Thank you, Ren=C3=A9
--
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

Re: mount errors

[Ken D'Ambrosio]

1) As of right now, btrfs's fsck is "done when it's done."  So don't ho=
ld your
breath, I'm afraid.

2) What errors do you get on mount?  It may be as simple as changing yo=
ur fstab
entry such that fsck isn't attempted to be run.  (Change the last colum=
n to
"0".) =20

-Ken


On Sat, 19 Nov 2011 14:01:41 +0100 Ren=C3=A9 Vangsgaard <rene.vangsgaar=
d@gmail.com>
wrote

> Hi - I have been using btrfs on /home for 2 weeks, and now it mounts
> with errors. I know that no fsck is available yet. I ignore the error
> and it still works, for now. Can I do anything to help you debug this
> problem with btrfs?
> Any news on fsck for btrfs?
>=20
> I am running Ubuntu 11.10.
> Thank you, Ren=C3=A9
> --
> 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





--
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

Re: mount errors

[René Vangsgaard]

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=3Dlzo,subvol=3D@home
I have tried removing the compress=3Dlzo with no difference.

-Ren=C3=A9

On 21 November 2011 17:27, Ken D'Ambrosio <ken@jots.org> wrote:
> 1) As of right now, btrfs's fsck is "done when it's done." =C2=A0So d=
on't hold your
> breath, I'm afraid.
>
> 2) What errors do you get on mount? =C2=A0It may be as simple as chan=
ging your fstab
> entry such that fsck isn't attempted to be run. =C2=A0(Change the las=
t column to
> "0".)
>
> -Ken
>
>
> On Sat, 19 Nov 2011 14:01:41 +0100 Ren=C3=A9 Vangsgaard <rene.vangsga=
ard@gmail.com>
> wrote
>
>> Hi - I have been using btrfs on /home for 2 weeks, and now it mounts
>> with errors. I know that no fsck is available yet. I ignore the erro=
r
>> and it still works, for now. Can I do anything to help you debug thi=
s
>> problem with btrfs?
>> Any news on fsck for btrfs?
>>
>> I am running Ubuntu 11.10.
>> Thank you, Ren=C3=A9
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrf=
s" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.h=
tml
>
>
>
>
>
>
--
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

Re: mount errors

[René Vangsgaard]

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 <ken@jots.org> wrote:
> 1) As of right now, btrfs's fsck is "done when it's done." =C2=A0So d=
on't hold your
> breath, I'm afraid.
>
> 2) What errors do you get on mount? =C2=A0It may be as simple as chan=
ging your fstab
> entry such that fsck isn't attempted to be run. =C2=A0(Change the las=
t column to
> "0".)
>
> -Ken
>
>
> On Sat, 19 Nov 2011 14:01:41 +0100 Ren=C3=A9 Vangsgaard <rene.vangsga=
ard@gmail.com>
> wrote
>
>> Hi - I have been using btrfs on /home for 2 weeks, and now it mounts
>> with errors. I know that no fsck is available yet. I ignore the erro=
r
>> and it still works, for now. Can I do anything to help you debug thi=
s
>> problem with btrfs?
>> Any news on fsck for btrfs?
>>
>> I am running Ubuntu 11.10.
>> Thank you, Ren=C3=A9
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrf=
s" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.h=
tml
>
>
>
>
>
>
--
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

Re: mount errors

[cwillu]

On Mon, Nov 21, 2011 at 5:29 PM, Ren=C3=A9 Vangsgaard
<rene.vangsgaard@gmail.com> 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-progs, which doesn't
understand lzo.

> My current mount options are
> defaults,compress=3Dlzo,subvol=3D@home
> I have tried removing the compress=3Dlzo with no difference.

Removing compress=3Dlzo doesn't remove compression from existing blocks=
=2E

Just disable fsck from running on boot (or update your progs from git).
--
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

Re: mount errors

[René Vangsgaard]

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=C3=A9

On 22 November 2011 05:55, cwillu <cwillu@cwillu.com> wrote:
> On Mon, Nov 21, 2011 at 5:29 PM, Ren=C3=A9 Vangsgaard
> <rene.vangsgaard@gmail.com> 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-progs, which doesn't
> understand lzo.
>
>> My current mount options are
>> defaults,compress=3Dlzo,subvol=3D@home
>> I have tried removing the compress=3Dlzo with no difference.
>
> Removing compress=3Dlzo doesn't remove compression from existing bloc=
ks.
>
> Just disable fsck from running on boot (or update your progs from git=
).
>
--
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

Re: mount errors

[cwillu]

On Tue, Nov 22, 2011 at 7:01 AM, Ren=C3=A9 Vangsgaard
<rene.vangsgaard@gmail.com> 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) t=
o
> use on kernel 3.0.0? Or just point me to a site with working
> instructions.

Sorry, the wiki is readonly and out-of-date (fallout from the kernel.or=
g woes).

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git is
receiving updates again, and should be what you want.
--
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

Re: mount errors

[René Vangsgaard]

I got the build working by changing -lpthread to -pthread in the gcc ca=
ll:

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 volumes.o utils.o btrfs-list.o btrfslabel.o
 -luuid

Using -lpthread gave a build error. I will now reboot and have a look..=
=2E

On 22 November 2011 14:06, cwillu <cwillu@cwillu.com> wrote:
> On Tue, Nov 22, 2011 at 7:01 AM, Ren=C3=A9 Vangsgaard
> <rene.vangsgaard@gmail.com> wrote:
>> I have decided to update progs from git. The instructions on the wik=
i
>> 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.
>
> Sorry, the wiki is readonly and out-of-date (fallout from the kernel.=
org woes).
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git i=
s
> receiving updates again, and should be what you want.
>
--
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

Re: mount errors

[Jan Schmidt]

On 22.11.2011 14:26, Ren=C3=A9 Vangsgaard wrote:
> I got the build working by changing -lpthread to -pthread in the gcc =
call:
>=20
> 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 volumes.o utils.o btrfs-list.o btrfslabel.=
o
>  -luuid
>=20
> Using -lpthread gave a build error. I will now reboot and have a look=
=2E..

We've already queued a fix for that, it's just not pushed out yet.
-Jan
--
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

Re: mount errors

[René Vangsgaard]

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-p=
rogs/.

On 22 November 2011 13:56, Jan Schmidt <list.btrfs@jan-o-sch.net> wrote=
:
> On 22.11.2011 14:26, Ren=C3=A9 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-map.o crc32c.o rbtree.o
>> extent-cache.o extent_io.o volumes.o utils.o btrfs-list.o btrfslabel=
=2Eo
>> =C2=A0-luuid
>>
>> Using -lpthread gave a build error. I will now reboot and have a loo=
k...
>
> We've already queued a fix for that, it's just not pushed out yet.
> -Jan
>
--
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

Re: mount errors

[René Vangsgaard]

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 file system.

-Ren=C3=A9

On 22 November 2011 15:24, Ren=C3=A9 Vangsgaard <rene.vangsgaard@gmail.=
com> wrote:
> 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 - stupi=
d
> 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 <list.btrfs@jan-o-sch.net> wro=
te:
>> On 22.11.2011 14:26, Ren=C3=A9 Vangsgaard wrote:
>>> I got the build working by changing -lpthread to -pthread in the gc=
c 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 volumes.o utils.o btrfs-list.o btrfslabe=
l.o
>>> =C2=A0-luuid
>>>
>>> Using -lpthread gave a build error. I will now reboot and have a lo=
ok...
>>
>> We've already queued a fix for that, it's just not pushed out yet.
>> -Jan
>>
>
--
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