bin/158756: newfs_msdos creates invalid image

David Naylor naylor.b.david at gmail.com
Sun Jul 10 08:30:11 UTC 2011


>Number:         158756
>Category:       bin
>Synopsis:       newfs_msdos creates invalid image
>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:   Sun Jul 10 08:30:10 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     David Naylor
>Release:        FreeBSD-current
>Organization:
Private
>Environment:
FreeBSD dragon.dg 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sat Jul  2 16:47:41 SAST 2011     root at dragon.dg:/tmp/home/freebsd9/src/sys/DRAGON  amd64
>Description:
newfs_msdos creates an invalid image.  A side affect of this is Windows XP sees the image as being full.  This error persists even after mounting and copying files to the image.  
>How-To-Repeat:
# newfs_msdos -F 32 /dev/da1
/dev/da1: 2014208 sectors in 62944 FAT32 clusters (16384 bytes/cluster)
BytesPerSec=512 SecPerClust=32 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 HugeSectors=2015232 FATsecs=492 RootCluster=2 FSInfo=1 Backup=2
# fsck_msdosfs /dev/da1
** /dev/da1
** Phase 1 - Read and Compare FATs
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (-1) not correct (62943)
Fix? [yn] y
1 files, 1007088 free (62943 clusters)

>Fix:
(Run fsck_msdosfs after creation)

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


More information about the freebsd-bugs mailing list