[H-GEN] Re: mkfs weirdness...

Doug South doug.south at gmail.com
Sun Jan 1 23:56:19 EST 2006


Obviously, I've done this enough to know how to do it without reading
any instructions, but I'm obviously not an admin. 8)

The kernel uses the old table until the next reboot, so the write not
taking is normal. And it seems that the JFS doesn't like the block
option.

Seems to be working now...

Just ignore this silly ol' developer... 8)

Regards,
Doug

On 1/2/06, Doug South <doug.south at gmail.com> wrote:
> Hi all,
>
> I'm getting some weird things happening while trying to mkfs some new
> partitions on my Debian etch system.
>
> The drive is 200GB (don't recall the brand off the top of my head, but
> I think it is a Seagate) partitioned as such:
>
> Command (m for help): p
>
> Disk /dev/hda: 200.0 GB, 200049647616 bytes
> 255 heads, 63 sectors/track, 24321 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/hda1               1          61      489951   82  Linux swap / Solaris
> /dev/hda2              62          63       16065   83  Linux
> /dev/hda3              64         185      979965   83  Linux
>
> The system works fine with no problems until I try to add new partitions.
>
> The first weird thing that happens is that when I add a new partition
> (whether primary or extended) and write and exit, mkfs doesn't see the
> changes made to the table until after a reboot. 8(
>
> Then, when I try to create the fs on the new partition, JFS reports:
>
> Log too large, no space for file system.
> The specified disk did not finish formatting.
>
> Which seemed a bit odd. So when I try ext3, it works, but the size is
> only 3.9M regardless of what size I've partitioned to table to! 8( df
> -h reports:
>
> /dev/hda5             3.9M  1.1M  2.7M  28% /mnt/hda5
>
> Any suggestions from the collective?
>
> Regards,
> Doug
> --
> blog = http://www.trontos.com/dsouth/blog/
>
> Any sufficiently complicated Java program requires a programmable IDE
> to make up for the half of Common Lisp not implemented in the program
> itself.
> -- Peter Seibel
>


--
blog = http://www.trontos.com/dsouth/blog/

Any sufficiently complicated Java program requires a programmable IDE
to make up for the half of Common Lisp not implemented in the program
itself.
-- Peter Seibel




More information about the General mailing list