linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12272] New: at random rmmod/insmod corrupts filesystem
Date: Mon, 22 Dec 2008 06:01:40 -0800 (PST)	[thread overview]
Message-ID: <bug-12272-13602@http.bugzilla.kernel.org/> (raw)

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

           Summary: at random rmmod/insmod corrupts filesystem
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.26 and 2.6.27
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: folkert@vanheusden.com


Latest working kernel version: 2.6.18
Earliest failing kernel version: 2.6.26
Distribution: Debian
Hardware Environment: P4 (with HT), IDE disk (PATA), 512MB ram
Software Environment: http://vanheusden.com/pyk/
Problem Description: filesystem corrupted:
[85202.195563] rtc0: alarms up to one month, y3k, hpet irqs
[85204.035802] journal_bmap: journal block not found at offset 2060 on dm-0
[85204.035818] Aborting journal on device dm-0.
[85311.242093] ext3_abort called.
[85311.242120] EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected
aborted journal
[85311.242154] Remounting filesystem read-only
[86331.285847] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76
[89931.353863] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76

[92499.263276] attempt to access beyond end of device
[92499.263296] dm-2: rw=17, want=4177066240, limit=6004736
[92499.263311] Buffer I/O error on device dm-2, logical block 522133279
[92499.263333] lost page write due to I/O error on dm-2
[92499.263341] Aborting journal on device dm-2.
[92499.263504] ext3_abort called.
[92499.263515] EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected
aborted journal
[92499.263543] Remounting filesystem read-only

[93531.419902] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76

Steps to reproduce: run pyk script and run something like a git clone of the
mainline kernel git tree, rm -rf the tree, touch /forcefsk, reboot


-- 
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:[~2008-12-22 14:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 14:01 bugme-daemon [this message]
2008-12-26 12:11 ` [Bug 12272] at random rmmod/insmod corrupts filesystem bugme-daemon
2008-12-26 14:16 ` bugme-daemon
2008-12-28 14:47 ` bugme-daemon
2009-01-05 19:52 ` bugme-daemon
2009-01-05 20:11 ` bugme-daemon
2009-01-05 21:50 ` bugme-daemon
2009-01-06 22:21 ` bugme-daemon
2009-01-06 23:57 ` bugme-daemon
2009-01-16  9:48 ` bugme-daemon
2009-01-16 19:37 ` bugme-daemon
2009-01-16 21:24 ` bugme-daemon
2009-01-17  2:23 ` bugme-daemon
2009-01-17 10:29 ` bugme-daemon
2009-01-17 10:34 ` bugme-daemon
2009-01-17 12:59 ` bugme-daemon
2009-01-17 13:47 ` bugme-daemon
2009-01-17 14:12 ` bugme-daemon
2009-01-17 16:13 ` bugme-daemon
2009-01-17 18:24 ` bugme-daemon
2009-01-17 18:27 ` bugme-daemon
2009-01-17 18:40 ` bugme-daemon
2009-01-17 18:43 ` bugme-daemon
2009-01-17 18:46 ` bugme-daemon
2009-01-17 18:56 ` bugme-daemon
2009-01-17 19:01 ` 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-12272-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).