[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: BUG: Entries in fstab with 'late' option, require order,
From:       John Baldwin <jhb () freebsd ! org>
Date:       2011-08-30 12:24:01
Message-ID: 201108300824.01387.jhb () freebsd ! org
[Download RAW message or body]

On Monday, August 29, 2011 2:08:46 pm rank1seeker@gmail.com wrote:
> This yields successfull boot
> --
> /dev/ufsid/4e5bbdf76b8b4567        /usr/DOC        ufs    rw,late  0  0
> /dev/ufsid/4e5bbe036b8b4567        /usr/SRC        ufs    ro,late,noatime  0  
0
> 
> # This are WinXP drives:
> /dev/ada0s1              /mnt/win_c      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> /dev/ada0s5              /mnt/win_d      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> /dev/ada0s6              /mnt/win_e      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> --
> 
> 
> This yields kick, in a single user mode
> --
> # This are WinXP drives:
> /dev/ada0s1              /mnt/win_c      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> /dev/ada0s5              /mnt/win_d      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> /dev/ada0s6              /mnt/win_e      ntfs    
rw,mountprog=/usr/local/bin/ntfs-3g,late         0       0
> 
> /dev/ufsid/4e5bbdf76b8b4567        /usr/DOC        ufs    rw,late  0  0
> /dev/ufsid/4e5bbe036b8b4567        /usr/SRC        ufs    ro,late,noatime  0  
0
> --
> 
> dmesg part:
> --
> Mounting late file systems:NTFS signature is missing.
> Failed to mount '/dev/ufsid/4e5bbdf76b8b4567': Invalid argument
> The device '/dev/ufsid/4e5bbdf76b8b4567' doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> NTFS signature is missing.
> Failed to mount '/dev/ufsid/4e5bbe036b8b4567': Invalid argument
> The device '/dev/ufsid/4e5bbe036b8b4567' doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> .
> Mounting /etc/fstab filesystems failed,  startup aborted
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
> Aug 29 20:02:31 blackhole init: /bin/sh on /etc/rc terminated abnormally, 
going
> to single user mode
> Enter full pathname of shell or RETURN for /bin/sh:

Hmm, seems like mountprog isn't being "cleared".  Try this patch to 
sbin/mount:

Index: mount.c
===================================================================
--- mount.c	(revision 225077)
+++ mount.c	(working copy)
@@ -589,6 +589,9 @@ mountfs(const char *vfstype, const char *spec, con
 		for (i = 1; i < mnt_argv.c; i++)
 			(void)printf(" %s", mnt_argv.a[i]);
 		(void)printf("\n");
+		free(optbuf);
+		free(mountprog);
+		mountprog = NULL;
 		return (0);
 	}
 
@@ -599,6 +602,8 @@ mountfs(const char *vfstype, const char *spec, con
 	}
 
 	free(optbuf);
+	free(mountprog);
+	mountprog = NULL;
 
 	if (verbose) {
 		if (statfs(name, &sf) < 0) {



> --
> 
> 
> Domagoj Smolčić
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> 

-- 
John Baldwin
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

[prev in list] [next in list] [prev in thread] [next in thread]