From: John Wyzer <john.wyzer@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck segmentation fault + trace
Date: Wed, 16 Jun 2010 22:25:13 +0200 [thread overview]
Message-ID: <4C193329.1000500@gmx.de> (raw)
In-Reply-To: <20100616172900.GA27466@think>
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 this email on 2.6.34.y.)
>
> But every time you boot 2.6.35 you get errors? Would it be possible to
> save the console output (netconsole works well)
[...]
device fsid 3247922091b53feb-dcb02f0506fbdc8b devid 1 transid 155748
/dev/mapper/root
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda4): warning: maximal mount count reached, running e2fsck is
recommended
EXT3-fs (sda4): using internal journal
EXT3-fs (sda4): recovery complete
EXT3-fs (sda4): mounted filesystem with writeback data mode
btrfs: fail to dirty inode 9959493 error -28
btrfs: fail to dirty inode 2987803 error -28
btrfs: fail to dirty inode 2987803 error -28
btrfs: fail to dirty inode 8873620 error -28
btrfs: fail to dirty inode 8873620 error -28
btrfs: fail to dirty inode 803894 error -28
btrfs: fail to dirty inode 2988335 error -28
btrfs: fail to dirty inode 2987971 error -28
btrfs: fail to dirty inode 2987972 error -28
btrfs: fail to dirty inode 2988336 error -28
btrfs: fail to dirty inode 6631 error -28
btrfs: fail to dirty inode 803896 error -28
btrfs: fail to dirty inode 6632 error -28
btrfs: fail to dirty inode 6633 error -28
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 logged via netconsole.
next prev parent reply other threads:[~2010-06-16 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:52 btrfsck segmentation fault + trace John Wyzer
2010-06-16 16:31 ` Chris Mason
2010-06-16 16:35 ` John Wyzer
2010-06-16 17:29 ` Chris Mason
2010-06-16 20:25 ` John Wyzer [this message]
2010-06-16 22:45 ` Yan, Zheng
2010-06-16 23:26 ` John Wyzer
2010-06-16 23:36 ` Yan, Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C193329.1000500@gmx.de \
--to=john.wyzer@gmx.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.