All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 23772] New: oops after mounting ext4 fs in 2.6.36.1 (failed to parse options in superblock)
Date: Thu, 25 Nov 2010 21:23:12 GMT	[thread overview]
Message-ID: <bug-23772-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=23772

           Summary: oops after mounting ext4 fs in 2.6.36.1 (failed to
                    parse options in superblock)
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.36.1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: fdziarmagowski@gmail.com
        Regression: No


Created an attachment (id=38222)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=38222)
output of tune2fs -l

I've just upgraded kernel to 2.6.36.1 and unfortunately some new features in
ext4 are deadly for my setup.
Mounting an external usb WD disk causes at first some dmesg activity:

Nov 25 21:10:01 aquarius kernel: EXT4-fs (sdb1): Unrecognized mount option
"ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ."
or missing value
Nov 25 21:10:01 aquarius kernel: EXT4-fs (sdb1): failed to parse options in
superblock:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ.
Nov 25 21:10:01 aquarius kernel: EXT4-fs (sdb1): mounted filesystem with
ordered data mode. Opts:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ.; (null)

And this is how it looks like with 2.6.35.x:
Nov 17 06:43:28 aquarius kernel: EXT4-fs (sdb1): recovery complete
Nov 17 06:43:28 aquarius kernel: EXT4-fs (sdb1): mounted filesystem with
ordered data mode. Opts: data=ordered

Just after mounting kernel is generating an oops, locking my system completely
(sysrq does not work!).

There are no special options passed to mount at mount time:
/dev/disk/by-label/MyBook    /mnt/mybook    ext4    noauto    0 0

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2010-11-25 21:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 21:23 bugzilla-daemon [this message]
2010-11-25 21:27 ` [Bug 23772] oops after mounting ext4 fs in 2.6.36.1 (failed to parse options in superblock) bugzilla-daemon
2010-11-25 21:31 ` bugzilla-daemon
2010-11-25 21:32 ` bugzilla-daemon
2010-11-26  2:57 ` bugzilla-daemon
2010-11-26 14:24 ` bugzilla-daemon
2010-11-26 14:27 ` bugzilla-daemon
2010-11-26 14:40 ` bugzilla-daemon
2010-11-26 14:45 ` bugzilla-daemon
2010-11-26 14:46 ` bugzilla-daemon
2010-11-26 20:45 ` bugzilla-daemon
2010-11-26 22:13 ` bugzilla-daemon
2010-11-29 19:34 ` bugzilla-daemon
2010-11-29 19:36 ` bugzilla-daemon
2010-11-29 21:55 ` bugzilla-daemon
2010-11-29 23:45   ` [PATCH] annotate superblock field offsets Andreas Dilger
2010-11-29 23:46     ` Eric Sandeen
2010-11-30 16:51 ` [Bug 23772] oops after mounting ext4 fs in 2.6.36.1 (failed to parse options in superblock) bugzilla-daemon
2010-11-30 17:50 ` bugzilla-daemon
2010-11-30 18:07 ` bugzilla-daemon
2010-11-30 20:54 ` bugzilla-daemon
2010-11-30 21:16 ` bugzilla-daemon
2010-12-01 14:58 ` bugzilla-daemon
2012-08-14 13:33 ` bugzilla-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-23772-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-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.