syslogd 378 root5w REG9,18548 192396
/var/log/boot.log
klogd 389 root2r REG8,1 191102 12
/boot/System.map-2.2.12-20
Is it safe to kill these?
These are loggers, so I guess nothing terrible would happen. But I
wouldn't kill them anyway..
[ Tuesday, October 26, 1999 ] Jakob Østergaard wrote:
Another solution is that raidtools, when old md support is
detected, issue a clear-like-water message like:
[snip]
While the newbies should be able to find the docs easily, we don't want
experienced users having to scroll thru
I'm using the 2.2.9-Kernel, RAID-Patch for the 2.2.10 Kernel
and raidtools 0.90.
"persistent-superblock" is set to 1 in /etc/raidtab
But the kernel simply doesn't start the RAID devices
at boot time.
kernel boot messages:
autodetecting RAID arrays
autorun ...
... autorun DONE.
/proc/mdsstat:
On Mon, Oct 25, 1999 at 05:59:37PM +, Marc Haber wrote:
Is commandname --help really the only documentation besides the
source code?
Nope --help is misleading, use the source :)))
One more thing: In a spare minute, I straced scsidev and found out
that it has a buglet: It obviously
Hi,
On Tue, 19 Oct 1999 20:12:20 -0700, "Tom Livingston" [EMAIL PROTECTED]
said:
Has anyone else tried raw-io with md devices? It works for me but the
performance is quite bad.
This is a recently reported issue on the linux-kernel mailing list.
The jist of it is that rawio is using a 512
On Oct 25, 8:33pm, Kenneth Cornetet wrote:
} Subject: RE: DPT Linux RAID.
Carefull on this! There are two EATA drivers. It's been several months since
I was trying this driver, but I believe the correct one is simply called
EATA. The ones *not* to use are called eata_dma and eata_pio. I got
Hi,
On Tue, 26 Oct 1999 11:42:41 -0400 (EDT), David Holl
[EMAIL PROTECTED] said:
would specifying differing input output block sizes with dd help?
Unfortunately not, no. The underlying device blocksize is set when the
device is first opened.
--Stephen
On Tue, 26 Oct 1999, Kent Nilsen wrote:
The hardware is a dual PIII500, 256Mb RAM, 3x50Gb Barracudas on a Mylex
AccelRaid250. OS: Mandrake 6.1 kernel 2.2.13.
With all those tiny files and a huge amount of disk space, be aware that
the latest version of mke2fs seems to "decide on a block
On Tue, 26 Oct 1999, G.W. Wettstein wrote:
The following is the .config option that needs to be set for reliable
operation with the DPT cards:
CONFIG_SCSI_EATA=y
We have not found the driver configured with the following define to be stable:
CONFIG_SCSI_EATA_DMA
The
At 09:07 26/10/99 -0600, Marcos Lopez wrote:
Egon Eckert wrote:
syslogd 378 root5w REG9,18548 192396
/var/log/boot.log
klogd 389 root2r REG8,1 191102 12
/boot/System.map-2.2.12-20
Is it safe to kill these?
These are
Hi out there!
I finally want to update my raid0-arrays to the 0.90 style raid. The
first thing I did was compiling raid-tools-0.90. That went fine.
I then converted my /etc/mdtab into a /etc/raidtab (please check them
for errors, they are attached).
Next step would be editing the init scripts to
(this was so's you can check if they are equivalent. TIA.)
# mdtab entry for /dev/md5
/dev/md5raid0,128k,0,008d4eba /dev/sda10 /dev/sdb10
# mdtab entry for /dev/md1
/dev/md1raid0,32k,0,7256556d/dev/sda5 /dev/sdb5 /dev/sdc5
# mdtab entry for /dev/md2
/dev/md2
[EMAIL PROTECTED] wrote:
snip
With all those tiny files and a huge amount of disk space, be aware that
the latest version of mke2fs seems to "decide on a block size" based on
partition size rather than default to 1kb blocks. I noticed this when Red
Hat 6.1 gave me a 2.5gb /var partition
Hello, thanks for the answer!
On Tue, 26 Oct 1999, Kent Nilsen wrote:
The hardware is a dual PIII500, 256Mb RAM, 3x50Gb Barracudas on a Mylex
AccelRaid250. OS: Mandrake 6.1 kernel 2.2.13.
With all those tiny files and a huge amount of disk space, be aware that
the latest version of
On Tue, 26 Oct 1999, Marc Mutz wrote:
With all those tiny files and a huge amount of disk space, be aware that
the latest version of mke2fs seems to "decide on a block size" based on
partition size rather than default to 1kb blocks. I noticed this when Red
Hat 6.1 gave me a 2.5gb /var
On Tue, 26 Oct 1999, Kent Nilsen wrote:
With all those tiny files and a huge amount of disk space, be aware that
the latest version of mke2fs seems to "decide on a block size" based on
partition size rather than default to 1kb blocks. I noticed this when Red
Hat 6.1 gave me a 2.5gb /var
In ka.lists.linux.raid, Luca wrote:
On Mon, Oct 25, 1999 at 05:59:37PM +, Marc Haber wrote:
One more thing: In a spare minute, I straced scsidev and found out
that it has a buglet: It obviously doesn't check the return code of
Was it rewitten recently?
I don't think so.
last time i
After setting up raid, the box is unable to autodetect the raid 1 array.
doing a cat /proc/mdstat shows that the array is not running however
when I type raidstart /dev/md0, then do a cat /proc/mdstat, everything is
fine
I'm running a stock rh 6.0 install. Where can i look to autodetect and
Kent Nilsen wrote:
snip
mke2fs -b 4096 -m 5 -i 8192 -R stride=128
snip x^^^ = 512k
You don't really have 0.5Mb chunk size, do you??
Marc
--
Marc Mutz [EMAIL PROTECTED]http://marc.mutz.com/
University of Bielefeld, Dep. of Mathematics /
hi, all
Hardware RAID help, please. Thanks.
I have a Compaq ProLiant 2500 Server using 2x
PPro200mhz, 128MB RAM, Compaq SmartArray 2/E EISA Card with 2x 4.3G and 1x 2.0G
HotSwappable HD.
but I cannot install RedHat 6.1 or SuSE 6.2, they
both cannot see my Smart 2/E.
Under RedHat 6.1, I
I've had a 9-gig SCSI Seagate drive in my machine for a while, and it's
mostly full. I've got two new drives and would like to build a RAID-5
with all three drives. Trouble is I don't have anywhere to backup what
I've got, so what I'd like to do is build my RAID 5 in degraded mode, and
copy all
I believe you're looking to set one of your three disks
as "failed-disk" as opposed to "raid-disk" in your
/etc/raidtab file. The device you give it is not even
actually accessed or written to; you could put /foo/bar
and it will still build degraded without and error, if I'm
not
22 matches
Mail list logo
