From: Jan Kasprzak <kas@informatics.muni.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: ext3+LVM - allocating block in system zone
Date: Sun, 23 Mar 2003 09:25:43 +0100 [thread overview]
Message-ID: <20030323092542.G20599@fi.muni.cz> (raw)
In-Reply-To: <20030321204342.A20599@fi.muni.cz>; from kas@informatics.muni.cz on Fri, Mar 21, 2003 at 08:43:43PM +0100
Jan Kasprzak wrote:
: Hello,
:
: I've got lots of the following messaegs today:
:
: EXT3-fs error (device lvm(58,0)): ext3_new_block: Allocating block in system zone - block = 205455454
: EXT3-fs error (device lvm(58,0)): ext3_new_block: Allocating block in system zone - block = 205455455
: EXT3-fs error (device lvm(58,0)): ext3_new_block: Allocating block in system zone - block = 205455456
: EXT3-fs error (device lvm(58,0)): ext3_new_block: Allocating block in system zone - block = 205455457
: EXT3-fs error (device lvm(58,0)): ext3_new_block: Allocating block in system zone - block = 205455461
:
: The system is newly-created LVM volume group with one LV (~820 GB)
: Extent size is 32MB, LV has its extents interleaved across six PVs.
:
: The ext3 filesystem is also newly created by the following command:
: mke2fs -j /dev/data_vg/export_lv -m 0 -R stride=8192 -J size=256
:
: The problem appeared when I started to copy data to this
: LV (about half an hour after the tar xvf - was started).
More info: no error has been reported by IDE layer.
XFS on the same LV works fine (2.4.20 + XFS patch + ptrace patch) -
I've restored 200+GB data from backup to the XFS volume (no FS error
reported), then unmounted the filesystem, rebooted and ran xfs_repair
- no inconsistencies were found. I've also checked MD5 sums of few files,
and it was OK. So it seems it is an ext2/ext3 problem.
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
|-- If you start doing things because you hate others and want to screw --|
|-- them over the end result is bad. --Linus Torvalds to the BBC News --|
prev parent reply other threads:[~2003-03-23 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 19:43 Jan Kasprzak
2003-03-23 8:25 ` Jan Kasprzak [this message]
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=20030323092542.G20599@fi.muni.cz \
--to=kas@informatics.muni.cz \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®