public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Stemen <linuxkernel@AdvancedResearch.org>
To: Nick Urbanik <nicku@vtc.edu.hk>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Cannot mount old ext2 cdrom, but e2fsck shows no problems
Date: Tue, 5 Jun 2001 03:37:03 -0500	[thread overview]
Message-ID: <01060503370300.10504@quark> (raw)
In-Reply-To: <3B1C8C1B.E3946FE1@vtc.edu.hk>
In-Reply-To: <3B1C8C1B.E3946FE1@vtc.edu.hk>

On Tuesday 05 June 2001 02:36, Nick Urbanik wrote:
> Dear folks,
>
> I made 18 ext2 cdroms in October 1998 using an old (new at the time) Red
> Hat system.  Now I can't mount them.  e2fsck shows no problems.  I also
> can dd them to a file, then mount the file.  But I want to be able to
> simply access them directly.  Current system: RH 7.1 with all updates.
>
> Sorry, I can't remember the exact command I used to create the images.
>
> I also want to better understand the output of dumpe2fs, and how to
> relate this to mount.
>

I think you are running into a block size issue.  I notice your fs
block size is only 1024.  See if you can mount it on an IDE CDROM
drive.  I ran into the same problem with file systems with a block
size of 1024 when using the ide-scsi module because it saw the device
bs as being 4096.  You cannot mount a file system with block size
smaller than the device.  I would unload the the ide-scsi modules and
mount it as /dev/hdxx and it mounted just fine.  I started specifying
the bs to be 4k when creating the file system to backup to CD and the
problem went away.  The error message was deceiving.  I did not
discover what it was until I left X windows and tried it from the
console and finally got an error relating to block size.

- Vincent Stemen

>
>
> $ dumpe2fs -h /dev/scd0
> dumpe2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> Filesystem volume name:   <none>
> Last mounted on:          <not available>
> Filesystem UUID:          7eb1b040-59f7-11d2-9e35-002018530df2
> Filesystem magic number:  0xEF53
> Filesystem revision #:    0 (original)
> Filesystem features:     (none)
> Filesystem state:         clean
> Errors behavior:          Continue
> Filesystem OS type:       Linux
> Inode count:              166624
> Block count:              665600
> Reserved block count:     33280
> Free blocks:              142206
> Free inodes:              153910
> First block:              1
> Block size:               1024
> Fragment size:            1024
> Blocks per group:         8192
> Fragments per group:      8192
> Inodes per group:         2032
> Inode blocks per group:   254
> Last mount time:          Fri Oct  2 21:06:45 1998
> Last write time:          Fri Oct  2 23:53:28 1998
> Mount count:              3
> Maximum mount count:      20
> Last checked:             Fri Oct  2 20:57:46 1998
> Check interval:           15552000 (6 months)
> Next check after:         Wed Mar 31 20:57:46 1999
> Reserved blocks uid:      0 (user root)
> Reserved blocks gid:      0 (group root)
>
> (I originally sent this to the Red Hat list, but there was no response).
>

  parent reply	other threads:[~2001-06-05  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  7:36 Cannot mount old ext2 cdrom, but e2fsck shows no problems Nick Urbanik
2001-06-05  7:59 ` Svein Erik Brostigen
2001-06-05  8:37 ` Vincent Stemen [this message]
2001-06-06  7:52   ` Nick Urbanik
2001-06-06 21:42 ` Pavel Machek

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=01060503370300.10504@quark \
    --to=linuxkernel@advancedresearch.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicku@vtc.edu.hk \
    /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