All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12629] New: EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone
Date: Tue,  3 Feb 2009 23:37:04 -0800 (PST)	[thread overview]
Message-ID: <bug-12629-13602@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=12629

           Summary: EXT3-fs error (device dm-1): ext3_new_block: Allocating
                    block in system zone
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.28.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: juris.krumins@ctco.lv


I'm experiencing problem with fs, reflected by the following errors:

...
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690639, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690640, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690641, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690642, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690643, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690644, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690645, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690646, length 1
EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone -
blocks from 537690647, length 1
...

Distribution  - CentOS 5.2
Hardware used - IBM x3650 with ServerRAID10K raid controller and EXP3000 disk
bay (12 SATA disks, RAID0. Total LD size ~8TB).
Tested with different default centos kernels (kernel-2.6.18-92.el5,
kernel-2.6.18-92.1.22.el5), the same
error. Tested also with custom 2.6.28.2 kernel and different FS flags, no
changes.
Hardware used - IBM x3650 with ServerRAID10K raid controller and EXP3000 disk
bay (12 SATA disks, RAID0. Total LD size ~8TB).
Right now running test on 2.6.28.2 with different FS flags, partition sizes and
so on. More that that, dm-crypt module is used
for this partition. But I think it's not dm-crypt related issue.


Right now I'm trying to update mu e2fsprogs utulities and run tests. Still
running and it's seems like FS, created with new e2fsprogs,
 looks more stable.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2009-02-04  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04  7:37 bugme-daemon [this message]
2009-02-04  9:08 ` [Bug 12629] EXT3-fs error (device dm-1): ext3_new_block: Allocating block in system zone bugme-daemon

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=bug-12629-13602@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --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 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.