On Thu, Feb 07, 2008 at 09:05:04AM +0100, Luca Berra wrote:
> On Wed, Feb 06, 2008 at 04:45:39PM +0100, Keld Jørn Simonsen wrote:
> >On Wed, Feb 06, 2008 at 10:05:58AM +0100, Luca Berra wrote:
> >>On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
> >>>Make each of the disks bootab
On Wed, Feb 06, 2008 at 04:45:39PM +0100, Keld Jørn Simonsen wrote:
On Wed, Feb 06, 2008 at 10:05:58AM +0100, Luca Berra wrote:
On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
>Make each of the disks bootable by lilo:
>
> lilo -b /dev/sda /etc/lilo.conf1
> lilo -b /dev/sdb
On Wed, Feb 06, 2008 at 10:05:58AM +0100, Luca Berra wrote:
> On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
> >Make each of the disks bootable by lilo:
> >
> > lilo -b /dev/sda /etc/lilo.conf1
> > lilo -b /dev/sdb /etc/lilo.conf2
> There should be no need for that.
> to achi
On Wed, Feb 06, 2008 at 08:24:37AM -0600, Moshe Yudkowsky wrote:
> I read through the document, and I've signed up for a Wiki account so I
> can edit it.
>
> One of the things I wanted to do was correct the title. I see that there
> are *three* different Wiki pages about how to build a system th
I read through the document, and I've signed up for a Wiki account so I
can edit it.
One of the things I wanted to do was correct the title. I see that there
are *three* different Wiki pages about how to build a system that boots
from RAID. None of them are complete yet.
So, what is the purp
Keld Jørn Simonsen wrote:
Make each of the disks bootable by grub
(to be described)
It would probably be good to show how to use grub shell's install
command. It's the most flexible way and give the most (or rather total)
control. I could write some examples.
-
To unsubscribe from this list
On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
Make each of the disks bootable by lilo:
lilo -b /dev/sda /etc/lilo.conf1
lilo -b /dev/sdb /etc/lilo.conf2
There should be no need for that.
to achieve the above effect with lilo you use
raid-extra-boot=mbr-only
in lilo.con
On Mon, Feb 04, 2008 at 07:38:40PM +0300, Michael Tokarev wrote:
Eric Sandeen wrote:
[]
http://oss.sgi.com/projects/xfs/faq.html#nulls
and note that recent fixes have been made in this area (also noted in
the faq)
Also - the above all assumes that when a drive says it's written/flushed
data, t
Linda Walsh wrote:
>
> Michael Tokarev wrote:
>> Unfortunately an UPS does not *really* help here. Because unless
>> it has control program which properly shuts system down on the loss
>> of input power, and the battery really has the capacity to power the
>> system while it's shutting down (anyo
Michael Tokarev wrote:
Unfortunately an UPS does not *really* help here. Because unless
it has control program which properly shuts system down on the loss
of input power, and the battery really has the capacity to power the
system while it's shutting down (anyone tested this?
Ye
On Sat, Feb 02, 2008 at 09:52:34PM +0100, Keld Jørn Simonsen wrote:
> On Sat, Feb 02, 2008 at 09:32:54PM +0100, Janek Kozicki wrote:
> > Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
> >
> > > This is intended for the linux raid howto. Please give comments.
> > > It
Michael Tokarev wrote:
note that with some workloads, write caching in
the drive actually makes write speed worse, not better - namely,
in case of massive writes.
With write barriers enabled, I did a quick test of
a large copy from one backup filesystem to another.
I'm not
On Mon, 4 Feb 2008, Michael Tokarev wrote:
Eric Sandeen wrote:
[]
http://oss.sgi.com/projects/xfs/faq.html#nulls
and note that recent fixes have been made in this area (also noted in
the faq)
Also - the above all assumes that when a drive says it's written/flushed
data, that it truly has.
Michael Tokarev wrote:
Unfortunately an UPS does not *really* help here. Because unless
it has control program which properly shuts system down on the loss
of input power, and the battery really has the capacity to power the
system while it's shutting down (anyone tested this? With new UPS?
an
Keld Jørn Simonsen wrote:
On Sun, Feb 03, 2008 at 10:53:51AM -0500, Bill Davidsen wrote:
Keld Jørn Simonsen wrote:
This is intended for the linux raid howto. Please give comments.
It is not fully ready /keld
Howto prepare for a failing disk
6. /etc/mdadm.conf
Something here on /etc/m
Eric Sandeen wrote:
> Moshe Yudkowsky wrote:
>> So if I understand you correctly, you're stating that current the most
>> reliable fs in its default configuration, in terms of protection against
>> power-loss scenarios, is XFS?
>
> I wouldn't go that far without some real-world poweroff testing,
Moshe Yudkowsky wrote:
> So if I understand you correctly, you're stating that current the most
> reliable fs in its default configuration, in terms of protection against
> power-loss scenarios, is XFS?
I wouldn't go that far without some real-world poweroff testing, because
various fs's are pro
Eric Sandeen wrote:
[]
> http://oss.sgi.com/projects/xfs/faq.html#nulls
>
> and note that recent fixes have been made in this area (also noted in
> the faq)
>
> Also - the above all assumes that when a drive says it's written/flushed
> data, that it truly has. Modern write-caching drives can wre
Eric,
Thanks very much for your note. I'm becoming very leery of resiserfs at
the moment... I'm about to run another series of crash tests.
Eric Sandeen wrote:
Justin Piszcz wrote:
Why avoid XFS entirely?
esandeen, any comments here?
Heh; well, it's the meme.
Well, yeah...
Note also
Justin Piszcz wrote:
> Why avoid XFS entirely?
>
> esandeen, any comments here?
Heh; well, it's the meme.
see:
http://oss.sgi.com/projects/xfs/faq.html#nulls
and note that recent fixes have been made in this area (also noted in
the faq)
Also - the above all assumes that when a drive says it'
Eric Sandeen wrote:
> Justin Piszcz wrote:
>
>> Why avoid XFS entirely?
>>
>> esandeen, any comments here?
>
> Heh; well, it's the meme.
>
> see:
>
> http://oss.sgi.com/projects/xfs/faq.html#nulls
>
> and note that recent fixes have been made in this area (also noted in
> the faq)
Actually, c
On Mon, 4 Feb 2008, Michael Tokarev wrote:
Moshe Yudkowsky wrote:
[]
If I'm reading the man pages, Wikis, READMEs and mailing lists correctly
-- not necessarily the case -- the ext3 file system uses the equivalent
of data=journal as a default.
ext3 defaults to data=ordered, not data=journa
Moshe Yudkowsky wrote:
[]
> If I'm reading the man pages, Wikis, READMEs and mailing lists correctly
> -- not necessarily the case -- the ext3 file system uses the equivalent
> of data=journal as a default.
ext3 defaults to data=ordered, not data=journal. ext2 doesn't have
journal at all.
> The
On Mon Feb 04, 2008 at 05:06:09AM -0600, Moshe Yudkowsky wrote:
> Robin, thanks for the explanation. I have a further question.
>
> Robin Hill wrote:
>
>> Once the file system is mounted then hdX,Y maps according to the
>> device.map file (which may actually bear no resemblance to the drive
>> ord
Robin, thanks for the explanation. I have a further question.
Robin Hill wrote:
Once the file system is mounted then hdX,Y maps according to the
device.map file (which may actually bear no resemblance to the drive
order at boot - I've had issues with this before). At boot time it maps
to the B
Michael Tokarev wrote:
Moshe Yudkowsky wrote:
[]
But that's *exactly* what I have -- well, 5GB -- and which failed. I've
modified /etc/fstab system to use data=journal (even on root, which I
thought wasn't supposed to work without a grub option!) and I can
power-cycle the system and bring it up
Moshe Yudkowsky wrote:
[]
> But that's *exactly* what I have -- well, 5GB -- and which failed. I've
> modified /etc/fstab system to use data=journal (even on root, which I
> thought wasn't supposed to work without a grub option!) and I can
> power-cycle the system and bring it up reliably afterward
On Sun Feb 03, 2008 at 02:46:54PM -0600, Moshe Yudkowsky wrote:
> Robin Hill wrote:
>
>> This is wrong - the disk you boot from will always be hd0 (no matter
>> what the map file says - that's only used after the system's booted).
>> You need to remap the hd0 device for each disk:
>> grub --no-flo
Moshe Yudkowsky wrote:
> Michael Tokarev wrote:
>
>> Speaking of repairs. As I already mentioned, I always use small
>> (256M..1G) raid1 array for my root partition, including /boot,
>> /bin, /etc, /sbin, /lib and so on (/usr, /home, /var are on
>> their own filesystems). And I had the following
Michael Tokarev wrote:
Speaking of repairs. As I already mentioned, I always use small
(256M..1G) raid1 array for my root partition, including /boot,
/bin, /etc, /sbin, /lib and so on (/usr, /home, /var are on
their own filesystems). And I had the following scenarios
happened already:
But th
Robin Hill wrote:
This is wrong - the disk you boot from will always be hd0 (no matter
what the map file says - that's only used after the system's booted).
You need to remap the hd0 device for each disk:
grub --no-floppy <
For my enlightenment: if the file system is mounted, then hd2,1 is a
Moshe Yudkowsky wrote:
> I've been reading the draft and checking it against my experience.
> Because of local power fluctuations, I've just accidentally checked my
> system: My system does *not* survive a power hit. This has happened
> twice already today.
>
> I've got /boot and a few other piec
On Sun Feb 03, 2008 at 01:15:10PM -0600, Moshe Yudkowsky wrote:
> I've been reading the draft and checking it against my experience. Because
> of local power fluctuations, I've just accidentally checked my system: My
> system does *not* survive a power hit. This has happened twice already
> to
I've been reading the draft and checking it against my experience.
Because of local power fluctuations, I've just accidentally checked my
system: My system does *not* survive a power hit. This has happened
twice already today.
I've got /boot and a few other pieces in a 4-disk RAID 1 (three ru
On Sun, Feb 03, 2008 at 10:53:51AM -0500, Bill Davidsen wrote:
> Keld Jørn Simonsen wrote:
> >This is intended for the linux raid howto. Please give comments.
> >It is not fully ready /keld
> >
> >Howto prepare for a failing disk
> >
> >6. /etc/mdadm.conf
> >
> >Something here on /etc/mdadm.conf. W
Keld Jørn Simonsen wrote:
This is intended for the linux raid howto. Please give comments.
It is not fully ready /keld
Howto prepare for a failing disk
The following will describe how to prepare a system to survive
if one disk fails. This can be important for a server which is
intended to alway
On Sat, Feb 02, 2008 at 09:32:54PM +0100, Janek Kozicki wrote:
> Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
>
> > This is intended for the linux raid howto. Please give comments.
> > It is not fully ready /keld
>
> very nice. do you intend to put it on http://lin
Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
> This is intended for the linux raid howto. Please give comments.
> It is not fully ready /keld
very nice. do you intend to put it on http://linux-raid.osdl.org/
As wiki, it will be much easier for our community to fi
This is intended for the linux raid howto. Please give comments.
It is not fully ready /keld
Howto prepare for a failing disk
The following will describe how to prepare a system to survive
if one disk fails. This can be important for a server which is
intended to always run. The description is mo
39 matches
Mail list logo
