-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've got the same problem. That is, I have a 2.6.35 btrfs volume that
segfaults and causes a kernel oops upon attempts to mount it. There is
some data on there that was not covered by the daily backup. Though it
is not the end of the world, I'd like t
On Sat, Jan 8, 2011 at 5:29 AM, cwillu wrote:
> On Fri, Jan 7, 2011 at 3:15 PM, Andrew Schretter
> wrote:
>> I have a 10TB btrfs filesystem over iSCSI that is currently unmountable. I'm
>> currently running Fedora 13 with a recent Fedora 14 kernel
>> (2.6.35.9-64.fc14.i686.PAE)
>> and the syst
On Fri, Jan 7, 2011 at 3:15 PM, Andrew Schretter wrote:
> I have a 10TB btrfs filesystem over iSCSI that is currently unmountable. I'm
> currently running Fedora 13 with a recent Fedora 14 kernel
> (2.6.35.9-64.fc14.i686.PAE)
> and the system hung with messages like :
>
> parent transid verify f
I have a 10TB btrfs filesystem over iSCSI that is currently unmountable. I'm
currently running Fedora 13 with a recent Fedora 14 kernel
(2.6.35.9-64.fc14.i686.PAE)
and the system hung with messages like :
parent transid verify failed on 5937615339520 wanted 48547 found 48542
I've rebooted and a
On Thu, Jun 17, 2010 at 7:26 AM, John Wyzer wrote:
> On 17/06/10 00:45, Yan, Zheng wrote:
>> On Thu, Jun 17, 2010 at 4:25 AM, John Wyzer wrote:
>>> btrfs: fail to dirty inode 6634 error -28
>>> [...] (nothing new coming, only error -28)
>>>
>>> Apart from that, I had messages that there was no s
On 17/06/10 00:45, Yan, Zheng wrote:
> On Thu, Jun 17, 2010 at 4:25 AM, John Wyzer wrote:
>> btrfs: fail to dirty inode 6634 error -28
>> [...] (nothing new coming, only error -28)
>>
>> Apart from that, I had messages that there was no space left on /, but
>> those were from userspace and not lo
On Thu, Jun 17, 2010 at 4:25 AM, John Wyzer wrote:
> On 16/06/10 19:29, Chris Mason wrote:
>> On Wed, Jun 16, 2010 at 06:35:25PM +0200, John Wyzer wrote:
Is 2.6.34 working normally?
>>>
>>> Yes. I can boot with 2.6.34.y and everything works fine. (Actually,
>>> before trying 2.6.45-rc3, I had
On 16/06/10 19:29, Chris Mason wrote:
> On Wed, Jun 16, 2010 at 06:35:25PM +0200, John Wyzer wrote:
>>> Is 2.6.34 working normally?
>>
>> Yes. I can boot with 2.6.34.y and everything works fine. (Actually,
>> before trying 2.6.45-rc3, I had an uptime of two weeks on this laptop.
>> Now, I'm writing
On Wed, Jun 16, 2010 at 06:35:25PM +0200, John Wyzer wrote:
> On 16/06/10 18:31, Chris Mason wrote:
> > On Wed, Jun 16, 2010 at 05:52:40PM +0200, John Wyzer wrote:
> >> I tried 2.6.35-rc3 and got error messages during the boot process about
> >> not being able
> >> to dirty inodes and no space lef
On 16/06/10 18:31, Chris Mason wrote:
> On Wed, Jun 16, 2010 at 05:52:40PM +0200, John Wyzer wrote:
>> I tried 2.6.35-rc3 and got error messages during the boot process about not
>> being able
>> to dirty inodes and no space left on device.
>
> Is 2.6.34 working normally?
Yes. I can boot with 2
On Wed, Jun 16, 2010 at 05:52:40PM +0200, John Wyzer wrote:
> I tried 2.6.35-rc3 and got error messages during the boot process about not
> being able
> to dirty inodes and no space left on device.
Is 2.6.34 working normally?
>
> 2.6.34.y runs fine and df -h shows
> rootfs296G
I tried 2.6.35-rc3 and got error messages during the boot process about not
being able
to dirty inodes and no space left on device.
2.6.34.y runs fine and df -h shows
rootfs296G 255G 39G 87% /
I reverted back to 2.6.34 and gave btrfsck a try resulting in a segmentation
fault
Hello,
when trying to btrfsck my filesystem, I got the following error:
# btrfsck /dev/sda7
parent transid verify failed on 13785038848 wanted 45848 found 45839
Segmentation fault
Crash occurs at extent-tree.c:find_first_block_group when it gets:
leaf = path->nodes[0];
13 matches
Mail list logo
