Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!news.kei.com!nntp.et.byu.edu!news.caldera.com!park.uvsc.edu!usenet
From: Terry Lambert <terry@cs.weber.edu>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: msdosfs causes total meltdown
Date: 18 Oct 1995 04:51:51 GMT
Organization: Utah Valley State College, Orem, Utah
Lines: 59
Message-ID: <462157$8jv@park.uvsc.edu>
References: <45ktg5$er0@ionews.io.org> <45p3mf$c84@uriah.heep.sax.de> <vmg2gsqc6u.fsf@block.statsci.com>
NNTP-Posting-Host: hecate.artisoft.com
scott@statsci.com (Scott Blachowicz) wrote:
] That's one of the things I tried on my 2.0.5R system at home. Since then
] I've seen mentions that seem to indicate that the messages like this:
]
] mountmsdosfs(): root directory is not multiple of clustersize length
It's a warning message and it's true. Ignore it. It means that
the FAT size is odd, in it's opinion.
] when the partition is mounted might indicate trouble. I was getting
] those messages.
It means that you did wierd things to the drive.
] Also, in fiddling with the mtools-2.0.7 code (the Debian/Linux
] version, at least - I'm working on a patch for the ports
] collection to incorporate their external configuration file code,
] so you don't have to recompile the source code just to add a
] new drive specification), I notice a check in there to see if
] the FAT is "right"...
]
] #ifdef CHK_FAT
] fat_size = (fat_bits == 12) ? (num_clus +2) * 3 / 2 :
] (num_clus +2) * 2;
] fat_size = (fat_size / 512) + ((fat_size % 512) ? 1 : 0);
] if (fat_size != fat_len) {
] fprintf(stderr, "fat_read: Wrong FAT encoding?\n");
] exit(1);
] }
] #endif /* CHK_FAT */
]
] I know my C: drive fails that test and I have a feeling that
] maybe it's a side effect of using FIPS to shrink the partition
] down.
It is, just like the warning message you got from msdosfs. It
means that given your partition size, you should have a smaller
default cluster size.
FIPS doesn't blow the cluster size when it changes the partition
size, and that's the "problem". The mtools code should not fail,
it should issue a warning as well (but is broken).
] And I have this vague bit of intuition that it is somehow
] related to the problems I had when I mounted the DOS slices.
] I haven't had the time or energy to re-slice & re-install my
] disk to verify that guess. I just stopped mounting my DOS
] slices from FreeBSD and everything's been hunky dory.
If the FS starts on a page boundry, you shouldn't have a real
problem. The msdosfs needs fixed.
Terry Lambert
terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.