Bug#569524: linux-image-2.6.26-2-686: cannot mount ext2 fs created by 2.6.30 but fsck is clean

[Bastian Blank <waldi@debian.org>]

tags 569524 moreinfo
thanks

On Fri, Feb 12, 2010 at 12:33:45AM -0500, David L. Craig wrote:
> # mount -vvvv /_/_ua
> mount: fstab path: "/etc/fstab"
> mount: lock path:  "/etc/mtab~"
> mount: temp path:  "/etc/mtab.tmp"
> mount: going to mount LABEL=_u0 by LABEL
> mount: spec:  "/dev/sdd"
> mount: node:  "/_/_ua"
> mount: types: "ext2"
> mount: opts:  "users,noamode"
> mount: mount(2) syscall: source: "/dev/sdd", target: "/_/_ua", filesystemtype: "ext2", mountflags: -1058209778, data: noamode
> mount: wrong fs type, bad option, bad superblock on /dev/sdd,
>        missing codepage or helper program, or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so

Any reason, why you did not check what exactly the kernel wants to tell
you?

> # tune2fs -l /dev/sdc1
> tune2fs 1.41.3 (12-Oct-2008)
> Filesystem volume name:   _u1
> Last mounted on:          <not available>
> Filesystem UUID:          67062ed5-8a8a-4863-84a4-289ee01d7c14
> Filesystem magic number:  0xEF53
> Filesystem revision #:    1 (dynamic)
> Filesystem features:      dir_index sparse_super large_file

large_file is marked as read-only compatible and supported since at
least 2.6.12.

> [163648.720862] EXT3-fs: mounted filesystem with ordered data mode.
> [165778.814712] ext3: No journal on filesystem on sdd

This is something completely different, it is no ext3.

Bastian

-- 
There is a multi-legged creature crawling on your shoulder.
		-- Spock, "A Taste of Armageddon", stardate 3193.9