On Mon, 27 Jun 2005, Otto Moerbeek wrote:
My work to fix the userland disk utilities (fdisk, disklabel, newfs)
to work properly on large file systems always has been handicapped
because I do not have very large disks. I think I managed to make all
legal block and fragment size combinations
On Sun, 26 Jun 2005, bofh wrote:
On 6/26/05, Otto Moerbeek [EMAIL PROTECTED] wrote:
On Sun, 26 Jun 2005, Ted Unangst wrote:
you changed a default and found a bug. less than 1% of users ever use
-m.
there's really no good reason to use -m 1, and several reasons not to
(not
On Mon, 27 Jun 2005, Otto Moerbeek wrote:
Try to reproduce the problem after having run fdisk (if it is
applicable, still don't know your platform, arghhh), disklabel and
newfs. If you can still reproduce the problem, I'll put this on my
TODO list, but not very high.
OK, you got me curious.
eric [EMAIL PROTECTED] writes:
On Sun, 2005-06-26 at 15:48:58 -0400, Ted Unangst proclaimed...
perhaps not, but not every knob is meant to cranked to the extremes.
there are more important things to be worked on than find out why newfs -m
1 doesn't work.
Definitely, and if I ever
On Sat, 25 Jun 2005, bofh wrote:
I tried a newfs -m 1 /dev/wd3a. After newfs is over, wd3a is not mountable.
fsck can't find any usable superblock. However, when I did a newfs
/dev/wd3a, the resulting partition checks out fine (fsck is ok with it) and
mounts without problems. Any idea why?
On Sun, 26 Jun 2005, Ted Unangst wrote:
On Sat, 25 Jun 2005, bofh wrote:
I tried a newfs -m 1 /dev/wd3a. After newfs is over, wd3a is not mountable.
fsck can't find any usable superblock. However, when I did a newfs
/dev/wd3a, the resulting partition checks out fine (fsck is ok with it)
On Sun, 26 Jun 2005, eric wrote:
you changed a default and found a bug. less than 1% of users ever use -m.
there's really no good reason to use -m 1, and several reasons not to (not
least of which is it apparently doesn't work). leave it alone and use the
default; you will be
On 6/26/05, Otto Moerbeek [EMAIL PROTECTED] wrote:
On Sun, 26 Jun 2005, Ted Unangst wrote:
you changed a default and found a bug. less than 1% of users ever use
-m.
there's really no good reason to use -m 1, and several reasons not to
(not
least of which is it apparently doesn't work).
Hi,
Just bought a WDC 250G HD. Model WD2500JB-00G.
I tried a newfs -m 1 /dev/wd3a. After newfs is over, wd3a is not mountable.
fsck can't find any usable superblock. However, when I did a newfs
/dev/wd3a, the resulting partition checks out fine (fsck is ok with it) and
mounts without problems.
9 matches
Mail list logo
