xfs
[Top] [All Lists]

Re: Ramdisk size etc

To: Eric Sandeen <sandeen@xxxxxxx>
Subject: Re: Ramdisk size etc
From: Juha Saarinen <juha@xxxxxxxxxxxx>
Date: Wed, 23 May 2001 13:16:45 +1200 (NZST)
Cc: "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <990579250.30985.0.camel@Porter>
Sender: owner-linux-xfs@xxxxxxxxxxx
On 22 May 2001, Eric Sandeen wrote:

> Here is how I understand this stuff:
>
> The value in the kernel is just the default for what the ramdisk size
> should be; passing a parameter to lilo overrides that.
>
> Also, this option just sets an upper bound on the size of the ramdisk.
> So I wouldn't worry TOO much about getting the size just right.
>
> (But FWIW, the size is set to the default 4086 (4M) in the RPM kernel
> configs)

Thanks, I wasn't sure what the upper limit should be. Set it to 4096.

> Configure.help says this:
>
>   Note that the APM support is almost completely disabled for
>   machines with more than one CPU.
>
> At one point there was a discussion about allowing a tiny subset of AMP
> functionality on SMP machines - basically, to allow soft power-off -
> since so few machines are supported by ACPI under Linux at this point.
>
> Since the configuration is _possible_, I assume (?) that it's safe, as
> implemented.

Well, I don't know, but:

# dmesg | grep apm
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.14)
apm: disabled - APM is not SMP safe.


Incidentally, I had a chance to test the robustness of XFS just now. I
fat-fingered the compile of the kernel modules, and left out that critical
little number after the -j parameter for make. The OOM Killer stepped in
after a while, and started butchering processes, so I couldn't Ctrl-C or
even halt the system. I reset the box, and it came back up just fine, as
quickly as a normal boot.

SCSI device sdb: 8813870 512-byte hdwr sectors (4513 MB)
 /dev/scsi/host0/bus0/target2/lun0: p1 p2 < p5 p6 p7 >
Start mounting filesystem: sd(8,22)
XFS: WARNING: recovery required on readonly filesystem.

XFS: write access will be enabled during mount.

Starting XFS recovery on filesystem: sd(8,22) (dev: 8/22)
Ending XFS recovery on filesystem: sd(8,22) (dev: 8/22)


Start mounting filesystem: sd(8,23)
Starting XFS recovery on filesystem: sd(8,23) (dev: 8/23)
Ending XFS recovery on filesystem: sd(8,23) (dev: 8/23)
Start mounting filesystem: sd(8,5)
Starting XFS recovery on filesystem: sd(8,5) (dev: 8/5)
Ending XFS recovery on filesystem: sd(8,5) (dev: 8/5)
Start mounting filesystem: sd(8,7)
Ending clean XFS mount for filesystem: sd(8,7)
Start mounting filesystem: sd(8,6)
Starting XFS recovery on filesystem: sd(8,6) (dev: 8/6)
Ending XFS recovery on filesystem: sd(8,6) (dev: 8/6)
Start mounting filesystem: sd(8,17)
Starting XFS recovery on filesystem: sd(8,17) (dev: 8/17)
Ending XFS recovery on filesystem: sd(8,17) (dev: 8/17)

-- that was it. Very nice. :-)






-- 
Regards,


Juha

PGP fingerprint:
B7E1 CC52 5FCA 9756 B502  10C8 4CD8 B066 12F3 9544



<Prev in Thread] Current Thread [Next in Thread>