SoftUpdate + BIG hd

SoftUpdate + BIG hd

Post by Kristensen Atle Frod » Wed, 04 Sep 2002 23:19:01



Since I am about/close to throw away my main Linux system (hd: 110 GB, +
mostly XFS file system ( / is ext2, mounted with sync-option) , will maybe
need more space later...) for OpenBSD :) -  I Have a router/firewall who
works great, tried softupdate, but have quirks some times, so I have
disabled this. Have't experienced any problem with my dear router's ffs (406
MB hd) without softupdates yet and my quirky electricy.

But mostly - what about 60-70 GB partition, and when the electricy is
dissappearing - will the fsck'ing take LONG time?

Have't experienced any problem with my dear router's ffs (406 MB hd)
without softupdates yet.
I have'nt UPS yet, and my electricy is also a little quirky sometimes.

So softupdates is usable/stable enought for production use?
I DEMAND max uptimes and minimal quirks  ;)

Atle Kristensen
Live Long And Prosper

 
 
 

SoftUpdate + BIG hd

Post by tedu » Thu, 05 Sep 2002 04:24:29



> But mostly - what about 60-70 GB partition, and when the electricy is
> dissappearing - will the fsck'ing take LONG time?

Yes.  The larger the filesystem, the longer fsck takes.

Quote:> So softupdates is usable/stable enought for production use?

softupdates is probably better than non-softupdates, but has no effect on
fsck times right now.

--
Mediocrity is a sin.

 
 
 

SoftUpdate + BIG hd

Post by Kristensen Atle Frod » Thu, 05 Sep 2002 18:24:36


["tedu" : ]


> > But mostly - what about 60-70 GB partition, and when the electricy is
> > dissappearing - will the fsck'ing take LONG time?

> Yes.  The larger the filesystem, the longer fsck takes.

> > So softupdates is usable/stable enought for production use?

> softupdates is probably better than non-softupdates, but has no effect on
> fsck times right now.

Thanks. And fsck takes long times at BIG hardisks.
But likes softupdates yes. quick rm -rf /some-ugly-directory  ;)

May install OpenBSD at test-machine (30 GB) and test this really hard.
To test before something before "production"-use is something I like to do
(and must ;) )

AFK
LLAP

 
 
 

SoftUpdate + BIG hd

Post by tedu » Thu, 05 Sep 2002 22:56:39



> It has: you can skip fsck safely. (Just to not skip it any more,
> you'll need to fsck -fy manually, a fsck -p will not make the drive
> clean (even if it says) -> fsck every boot)

I didn't want to say that, since I don't think it's the best practice.  It
should be safe though.  Still waiting for background fsck....

--
Mediocrity is a sin.

 
 
 

SoftUpdate + BIG hd

Post by tedu » Fri, 06 Sep 2002 06:16:08



>Du hast eine [...] Startseite ohne graphischen Schwachfug. [...] Wenn
>qmail ohne Not [...] auf der Gegenseite Resourcen verbrt ist das genau so,
>als ob Du als Web-Designer auf der Gegenseite ein Java-Programm starten
>willst, um ein <a href> zu simulieren. Es ist Scheie und gehrt bestraft.

er, putty mangled the special letters in that.  What's a Schwachfug?  And
a Gegenseite?  They don't seem to mean what I think they do. :(

--
Mediocrity is a sin.

 
 
 

1. Big (REALLY BIG) HD storage & Linux

Okie..allow me to apologize in advance, as this will be long, and
contain many questions:)

I've read (and read and read) to determine if there are limiting
factors to the amount of HD space mountable under Linux.
We are setting up a POP to support the student population of a small
campus, and a storage minimum of 5MB per student has been established.
My understanding from the SCSI-HOWTO is that Linux can handle drives
up to a Terabyte. what we actually need is the ability to handle at
least 61Gig
Questions:
1. Is there a memory limitation similar to novell in that novell must
have enough memory to hold the tables for the volume size it is
mounting. I seem to remember reading somewhere (and I've tried to find
it) that Linux uses memory for the inodes on the drive....if so, how
much does it require?

2. If it does require memory, is it possible to boot linux from a
smaller partition (obviously we have to boot from one with < 1024 cyl
anyway), then, mount the extra partitions AFTER mounting the swap
partitions? (i.e. will the inode tables be swapped to the swapfile and
allow us to mount the huge partitions that way)

3. If that doesn't work, would it be possible to spread things out a
bit by adding additional servers and mounting thier volumes as NFS,
then use them for the users home directories? (i.e. what are the
memory requirements for mounting an NFS volume...obviously less than
mounting a physical drive that large, but how much less?)

4. Has anyone made use of the NFS volume provided by IBM Lan File
Services/ESA with a Linux system? (for humor I should interject here
that I thought the Mainframers were gonna pass out when we told them
in a meeting we wanted to consider sucking up 61Gig of thier shiny new
DASD...I thought the tape backup guy was gonna have a heart attack
when we started talking about ADSM:) and the IBM rep went all starry
eyed like he was gonna retire after selling us another one maybe:)

5. On a little different track, has anyone thought of a nifty way to
place user home directories under home but on another drive?
I've considered rranging them under home/home1/user...home/home2/user,
but maybe someone knows of a better way that would require a less
complicated script (we're importing a list), and less administration:)

6. Anyone had any experience (read problems) running Linux on a Compaq
Prosignia 5000 server?

I know this is long, and I apologize once again. While I've run Linux
for a while, I've never seen anyone talk about mounting more than
about 10Gig....so I thought I'd best check out the answers to this
stuff prior to committing myself to administrative hell:)

Thanks,
Steve Walker

2. unix-admin-horror-stories where ?

3. Big Big Big CORE Image !!

4. Gnome

5. I have a BIG, BIG,BIG problem with DOSEMU 0.98.5.

6. Konqueror can't handle hpps://.banking.diba.de

7. Big, Big Very BIG SCSI DISK

8. X Windows and 3D Blaster...hehe

9. How big a HD for Linux box?

10. big IDE HD, use LILO?

11. Big HD Problem

12. Bios dont boot BIg HD

13. BIG HD's