> At 12:44 25/07/02, Alexander Viro wrote:
> >Al, still thinking that anybody who does mkfs.<whatever> on a multi-Tb
> >device should seek professional help of the kind they don't give on l-k...
>
> Why? What is wrong with large devices/file systems? Why do we have to break
> up everything into multiple devices? Just because the kernel is "too lazy"
> to implement support for large devices? Nobody cares if 64bit code is
Large filesystem => troubles with backups, even more troubles with restoring
after disk failure, yadda, yadda.
> database server and we can live with that. At least our applications deal
> with GiBs of data for each experiment, which is shifted over Gigabit
> ethernet to/from a SQL database backend stored on a huge RAID array, so we
> are completely i/o bound.
>
> It's one database, and it's huge. And it's going to get bigger as people do
> more experiments. We need mkfs.<whatever> on a huge device... We are just
> lucky that our current RAID array is under 2TiB se we haven't hit the
> "magic" barrier quite yet. But at 1.4TiB we are not far off...
... and backups of your database are done on...?
"RAID" doesn't mean that data is safe. It means that some class of
failures will not be immediately catastrophic, but that's it - both
hardware and software arrays _do_ go tits up. Just ask hpa for story
of the troubles on kernel.org.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/