From reg@clemens.dwf.com Sun Mar 14 15:24:36 1999
Return-Path: <reg@clemens.dwf.com>
Received: from clemens.dwf.com (clemens.dwf.com [204.134.2.17])
	by hub.freebsd.org (Postfix) with ESMTP id F171914F5C
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 14 Mar 1999 15:23:25 -0800 (PST)
	(envelope-from reg@clemens.dwf.com)
Received: (from reg@localhost)
	by clemens.dwf.com (8.8.5/8.8.5) id PAA25342
	for FreeBSD-gnats-submit@freebsd.org; Sun, 14 Mar 1999 15:56:44 -0700 (MST)
Message-Id: <199903142256.PAA25342@clemens.dwf.com>
Date: Sun, 14 Mar 1999 15:56:44 -0700 (MST)
From: Reg Clemens <reg@dwf.com>
Sender: reg@clemens.dwf.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: EXT2FS mount problems.

>Number:         10594
>Category:       kern
>Synopsis:       EXT2FS mount problems
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 14 15:30:00 PST 1999
>Closed-Date:    Sat Nov 17 09:00:43 PST 2001
>Last-Modified:  Sat Nov 17 09:00:55 PST 2001
>Originator:     Reg Clemens
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
<R.W.Clemens, Consulting>
>Environment:

350MHz Pentium, 64MB memory, 2x 6GB IDE drives.
Machine multiboots W98, Linux, Solaris7, FreeBSD.
Clean Re-install of FreeBSD 3.1 (same problem when I did an upgrade from 3.0)

>Description:

Having rebuilt the GENERIC kernel, adding `options "EXT2FS"'
I can copy to/from the ext2fs, but trying to make a directory over
there causes the entire system to hang.  Have to powercycle to get out.
Yet others claim that it works for them!

>How-To-Repeat:

	Add the line
	options "EXT2FS"
	to GENERIC, and rebuild the kernel.
	then mount the ext2fs
	try copying to/from it, this should work.
	then cd into it, and try `mkdir abc'
	the system will hang.

>Fix:

	Unknown.

> ADDITIONAL INFORMATION.

Here are some more details that should help

---

(1) If the ext2fs needs fsck run on it (after one of these attempts to mkdir
from FreeBSD), then the NEXT attempt from FreeBSD to mount the filesystem will
give

rion# /sbin/mount -t ext2fs /dev/wd2s1 /mnt
xt2fs: /dev/wd2s1: Operation not permitted
rion#

which is very non-descript.

---

(2) If the file system is in GOOD SHAPE, then the mount proceeds with no
problems, I can copy to/from the file system, but trying to make a directory
over there causes the entire system to hang.

AT THE TIME OF THE MOUNT, the following messages get written to the
/var/log/messages file.

   Mar 14 01:42:12 orion /kernel: wd2s1: raw partition size != slice size
   Mar 14 01:42:12 orion /kernel: wd2s1: start 63, end 12225464, size 12225402
   Mar 14 01:42:12 orion /kernel: wd2s1c: start 63, end 2072384, size 2072322

These numbers dont make much sense.  The `63' would make me assume that the
units are sectors (1 track for the label).  The disk is a 6.3GB disk, with
a large 1st `slice' of almost 6.3GB, followed by a 125MB (swap) slice.
So the 2nd line is probably a good description of the `slice' being mounted.
I have NO idea what the 3rd line is trying to say,- PartitionMagic shows
everything is just fine, and Linux/Solaris have no problems with the disk.

In one case when trying to `mkdir abc' I got an error message on the screen
(which I couldnt capture since the machine was frozen) but here is what
I wrote down

    panic read_inode_bitmap cannot read inode bitmap -
    block_group = 306, inode_bitmap = 2506779

---

My current FreeBSD `slice' is only 900MB or so, since I had problems with the
initial 3.0 install, and didnt want to tempt fate by trying to repartion.
So to do anything useful I REALLY do have to mount that ext2fs to get some
working space.

					Reg.Clemens
					reg@dwf.com

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: steve 
Responsible-Changed-When: Sun Mar 14 19:20:20 PST 1999 
Responsible-Changed-Why:  
Misfiled PR. 
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 17:57:26 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=10594 
State-Changed-From-To: feedback->closed 
State-Changed-By: bmah 
State-Changed-When: Sat Nov 17 09:00:43 PST 2001 
State-Changed-Why:  
Feedback timeout (3+ months). 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=10594 
>Unformatted:
