That's all well and good..but what about the configuration files? They are
text and are not redundant in the same way. I know it's been done to
death..and I've read a lot of this stuff, but even after making thanges,
etc, especially if I use logbufs > 2, I can make this happen at will. That's
why I've got concerns. I know about the points Keith made, and very valid in
this case especially, but my major concern is deploying a TB size db only to
get taken down that my configs are messed up. (yes, I know that's what
backups and CVS are for) but that's not acceptable when talking about my
primary FS. I'm going to go through as many iterations of this as I can to
see if I can narrow down exactly what and where, what hardware, etc. We're
about to do a major deployment and I'm just trying to do due dilligence,
beyond the FAQ and random mails. Thanks for listening, and this can
certainly come off-list if you feel that's best. I really don't want to beat
a dead horse anymore than I have to. Assurance of success in this respect is
very important. We don't have a lot of storage to throw around.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@xxxxxxxxxxxxxxx
> -----Original Message-----
> From: Seth Mos [mailto:knuffie@xxxxxxxxx]
> Sent: Sunday, September 02, 2001 7:18 PM
> To: Gonyou, Austin; XFS mailing list
> Subject: Re: System lock while accessing files causes file corruption
>
>
> At 18:16 2-9-2001 -0500, Gonyou, Austin wrote:
> >Why is this? If I open a file, text/otherwise and the power
> actually fails,
> >(i turn it off), once in a while I get a corrupt file. Why
> is this? What
> >would happen if I was writing to some Oracle filesystems and
> this situation
> >occurred? Please advise.
>
> See the http://oss.sgi.com/projects/xfs/faq.html#nulls
>
> A database would survive since most have their own buffering and
> transaction scheme.
>
>
> --
> Seth
> Every program has two purposes one for which
> it was written and another for which it wasn't
> I use the last kind.
>
|