Bug#569524: linux-image-2.6.26-2-686: cannot mount ext2 fs created by 2.6.30 but fsck is clean
On Fri, Feb 12, 2010 at 09:26:25AM +0100, Bastian Blank wrote:
> tags 569524 moreinfo
> thanks
No, thank YOU! You probably don't want to think about how much
this would be costing me if you were working on this problem for
the benefit of Microsoft versus how much _you_ would be getting.
> Any reason, why you did not check what exactly the kernel wants to tell
> you?
Ignorance? What do I need to do to get it to spit out what would
be helpful?
> large_file is marked as read-only compatible and supported since at
> least 2.6.12.
muse:~# mount -vvvv -L _u1 -o ro
mount: fstab path: "/etc/fstab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: going to mount LABEL=_u1 by LABEL
mount: spec: "/dev/sdc1"
mount: node: "/_/_ub"
mount: types: "ext2"
mount: opts: "users,noamode,ro"
mount: mount(2) syscall: source: "/dev/sdc1", target: "/_/_ub", filesystemtype: "ext2", mountflags: -1058209777, data: noamode
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
muse:~#
> > [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.
I believe I tried an ext3 definition to determine if that
might mount. The first line cited refers to a different
device.
--
May the LORD God bless you exceedingly abundantly!
Dave_Craig______________________________________________
"'So the universe is not quite as you thought it was.
You'd better rearrange your beliefs, then.
Because you certainly can't rearrange the universe.'"
__--from_Nightfall_by_Asimov/Silverberg_________________
Reply to: