[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Big disk - solutions
- To: misc_(_at_)_openbsd_(_dot_)_org, tech_(_at_)_openbsd_(_dot_)_org
- Subject: Big disk - solutions
- From: Letty Foulkes <foulkes_(_at_)_ultdev_(_dot_)_chess_(_dot_)_cornell_(_dot_)_edu>
- Date: Thu, 22 Mar 2001 16:39:35 -0500 (EST)
Thanks to all that responded to my question - solutions have been found
based on some of your contributions. My RAID is mounted and consistent
(fdisk and disklabel) and has no problem with fsck.
For anyone that has the same problem - apparently the superblock has
a region for pointers to the cylinders/group information. If this is
too large it overflows and the superblock gets corrupted. There is also
a fix for forcing fdisk to accept a larger than 1023 cylinders.
I applied the two workarounds suggested by Grigoriy Orlov:
1) Divided the RAID into two partitions of about 270Gbytes each.
2) Created the fs with "newfs -c 64 /dev/rsd0d" which increases the number of
cylinders per group to 64 (rather than the default of 16).
And I also run fdisk with the suggestions found in:
which Nick Holland pointed to.
Thanks again and keep up the good work.