On Sun, 16 May 1999, Archie Cobbs wrote:
> Alex Le Heux writes:
> > Maybe I'm completely wrong here, but didn't I read somewhere that with
> > softupdates it would theoretically be possible to boot the system before
> > the fsck and fsck while it's running?
>
> Yes.. if you make the assumptions t
Alex Le Heux writes:
> Maybe I'm completely wrong here, but didn't I read somewhere that with
> softupdates it would theoretically be possible to boot the system before
> the fsck and fsck while it's running?
Yes.. if you make the assumptions that:
1. There are no bugs in the soft updates code
Jim Carroll wrote:
>
> I was wondering if anyone has done any work on fsck and very large file
> systems. We have a system that has 126 GB RAID Array. As you can imagine,
> fsck chokes trying to alloc enough blocks to store it's internal data
> structures (128 MB RAM, 128 MB Swap)
"Mark J. Taylor" writes:
> The problem that we ran into in a system with several 130 MB RAID5 arrays
> is that the fsck was running out of RAM+swap. We had to add a vnode to swap
> to before the fsck would complete (basically added more swap space).
> We had to have over 100 MB swap space to fsck
Chuck Youse wrote:
> Whoa ... can anyone substantiate that this poor performance is typical
> or atypical of DPT SCSI RAID controllers?
This is atypical, however DPT HBAs are *very* touchy about termination
and cabling. For instance, with two identical (old) Seagate Hawks on
a SmartCache III, I g
Whoa ... can anyone substantiate that this poor performance is typical
or atypical of DPT SCSI RAID controllers?
I was just about to drop $6000 on a DPT SmartRAID IV 64MB. . .
Chuck Youse
Director of Systems
cyo...@cybersites.com
On Thu, 13 May 1999, Greg Lehey wrote:
> On Wednesday, 12 May
On Wednesday, 12 May 1999 at 15:18:22 -0400, Mark J. Taylor wrote:
> On 12-May-99 Matthew Jacob wrote:
>>
>>
I was wondering if anyone has done any work on fsck and very large
file
systems. We have a system that has 126 GB RAID Array. As you can
imagine,
fsck ch
On Wed, May 12, 1999 at 01:38:00PM -0400, a little birdie told me
that Jim Carroll remarked
>
> I was wondering if anyone has done any work on fsck and very large file
> systems. We have a system that has 126 GB RAID Array. As you can imagine,
> fsck chokes trying to alloc enough bl
> >
> > I've been doing 120GB+ filesystems for FreeBSD for quite some time. The
> > real fun will be the 1TB filesystems.
>
> How much Swap disk space have you allocated on machines that you fsck'ed
> that were this large ?
Well, here's a current FreeBSD machine that has a couple 60GB raid bo
> > > I was wondering if anyone has done any work on fsck and very large
> > > file
> > > systems. We have a system that has 126 GB RAID Array. As you can
> > > imagine,
> > > fsck chokes trying to alloc enough blocks to store it's internal
> > > data
> > > structures (128 MB RAM
:
:
: I was wondering if anyone has done any work on fsck and very large file
: systems. We have a system that has 126 GB RAID Array. As you can imagine,
: fsck chokes trying to alloc enough blocks to store it's internal data
: structures (128 MB RAM, 128 MB Swap)
:
: We would like to
The problem that we ran into in a system with several 130 MB RAID5 arrays
is that the fsck was running out of RAM+swap. We had to add a vnode to swap
to before the fsck would complete (basically added more swap space).
We had to have over 100 MB swap space to fsck the 130 MB volume, and the
syste
> > I was wondering if anyone has done any work on fsck and very large file
> > systems. We have a system that has 126 GB RAID Array. As you can imagine,
> > fsck chokes trying to alloc enough blocks to store it's internal data
> > structures (128 MB RAM, 128 MB Swap)
Huh- I reme
> I was wondering if anyone has done any work on fsck and very large file
> systems. We have a system that has 126 GB RAID Array. As you can imagine,
> fsck chokes trying to alloc enough blocks to store it's internal data
> structures (128 MB RAM, 128 MB Swap)
Might not the use of
14 matches
Mail list logo
