Hi Miao,
ok, i'll try:
mkfs.ext3 /dev/sdaN
»used it as root-file-system quite a while«
tune2fs -O extents,uninit_bg,dir_index /dev/sdaN (converted to ext4)
»used it as root file system quite another while«
btrfs-convert /dev/sdaN (converted to btrfs)
»used it as root filesystem with "-compress"
Von: Miao Xie
An: Adi
CC: liubo2...@cn.fujitsu.com, linux-btrfs@vger.kernel.org
Betreff: Re: wanted X found X-1 but you got X-2
Hi, Adi
On Sat, 31 Jul 2010 18:34:24 +0200, Adi wrote:
ok, i have tried the 2.6.35-rc6 kernel, as TiCPU on #btrfs suggested,
but i also got an error. i don't think it
2 Aug 2010 09:04:27 +0800
> Von: Miao Xie
> An: Adi
> CC: liubo2...@cn.fujitsu.com, linux-btrfs@vger.kernel.org
> Betreff: Re: wanted X found X-1 but you got X-2
> Hi, Adi
>
> On Sat, 31 Jul 2010 18:34:24 +0200, Adi wrote:
> > ok, i have tried the 2.6.35-rc6 kernel,
Hi, Adi
On Sat, 31 Jul 2010 18:34:24 +0200, Adi wrote:
ok, i have tried the 2.6.35-rc6 kernel, as TiCPU on #btrfs suggested, but i
also got an error. i don't think it has something to do with kcrypt, as i can
mount another partition without any problems.
[snip]
[ cut here ]--
ok, i have tried the 2.6.35-rc6 kernel, as TiCPU on #btrfs suggested, but i
also got an error. i don't think it has something to do with kcrypt, as i can
mount another partition without any problems.
hm, and btw, that dump was made on another pc.
here is a dmesg-dump:
*
hi,
i used a current stable gentoo with a 2.6.34-r2 gentoo-kernel. the btrfs
filesystem is on a lvm, which is on a luks-partition.
i think i corrupted the filesystem with a 2.6.34 tuxonice kernel, witch ran
fine without suspend-to-disk, but after suspending i couldn't reboot anymore.
this debug
On 07/29/2010 09:11 PM, Adi wrote:
> hi,
> i have a problem with mounting a btrfspartition. i think it corrupted
> somehow. btrfsck also didn't work.
> here is the demesg output, if i try to btrfsck it:
>
>
Hi, Adi
can you give us some steps with which the bug can be reproduced?
Thanks,
liub
hi,
i have a problem with mounting a btrfspartition. i think it corrupted somehow.
btrfsck also didn't work.
here is the demesg output, if i try to btrfsck it:
***
device-mapper: ioctl: unable to remove open device temporary-cryptsetup-2466
device fsid 184f65b363e