misc/118113: mdconfig init script requires image to be on root file system

[Steve Wills]

>Number:         118113
>Category:       misc
>Synopsis:       mdconfig init script requires image to be on root file system
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 19 04:10:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Steve Wills
>Release:        7.0-BETA3
>Organization:
>Environment:
>Description:
/etc/rc.d/mdconfig requires that images be on the root file system. This script would be good for having images of jails mounted at boot, but I don't want to keep them on root file system, nor do I have room. Most users don't have room either, given the default root fs size(s). It might also be useful for having an ISO image mounted at boot. Is there a reason for the requirement that the image be on the root file system?

Also, even if the file is on /, and you apply the patch in PR conf/118035, you still get this error:

# /etc/rc.d/mdconfig start
Creating md0 device (vnode).
fsck: Could not determin filesystem type
Fsck failed on /dev/md0, not mounting the filesystem.
>How-To-Repeat:
  dd if=/dev/zero of=/tmp/jail.img bs=1 count=1 seek=2147483648
  echo 'mdconfig_md0="-f /tmp/jail.img"' >> /etc/rc.conf
  /etc/rc.d/mdconfig start

(This also returns no error, which may also be considered a bug).

  
>Fix:
Remove the check for root filesystem, add filessytem type of fsck command for UFS images, remove fsck all together for ISO images.

>Release-Note:
>Audit-Trail:
>Unformatted: