From: Badari Pulavarty <pbadari@us.ibm.com>
To: linux-ext4@vger.kernel.org
Subject: ext4 errors while runing fsx (2.6.25)
Date: Mon, 21 Apr 2008 17:18:53 -0700 [thread overview]
Message-ID: <1208823533.17986.48.camel@badari-desktop> (raw)
Got these messages while running fsx on ext4.
Known issue ?
Thanks,
Badari
EXT4 FS on hda1, internal journal
EXT4-fs: mounted filesystem with ordered data mode.
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
pa ffff8101cc8400b0: logic 8, phys. 9065, len 56
EXT4-fs error (device hda1): ext4_mb_release_inode_pa: free 37, pa_free 38
pa ffff8101cc8556b0: logic 32, phys. 8935, len 32
EXT4-fs error (device hda1): ext4_mb_release_inode_pa: free 21, pa_free 22
pa ffff8101cc85e8b0: logic 9, phys. 8971, len 55
EXT4-fs error (device hda1): ext4_mb_release_inode_pa: free 43, pa_free 44
pa ffff81017d0f7330: logic 39, phys. 9131, len 25
EXT4-fs error (device hda1): ext4_mb_release_inode_pa: free 20, pa_free 21
pa ffff8101bb1431b0: logic 18, phys. 33438, len 46
EXT4-fs error (device hda1): ext4_mb_release_inode_pa: free 26, pa_free 27
next reply other threads:[~2008-04-22 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 0:18 Badari Pulavarty [this message]
2008-04-23 8:45 ` ext4 errors while runing fsx (2.6.25) Aneesh Kumar K.V
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=1208823533.17986.48.camel@badari-desktop \
--to=pbadari@us.ibm.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox