You are right Puchar, but sometimes (2 in 100 on powerfailure) the
filesystem
gets corrupted (database files opened, and being extended)... so
when the fsck enters, the database get corrupted..
Filesystem will rather be not corrupted, but database file data.
Non-journalled UFS with softupdate
Em Sáb, 2009-06-06 às 23:13 +0200, Wojciech Puchar escreveu:
> > try to use journaling on the backup partition, (if you do not want to
> > use ZFS...)
>
> is it THAT a problem to wait 5-10 minutes for fsck?
>
> on OS that really crash RARELY. Most cases not at all.
You are right Puchar, but so
try to use journaling on the backup partition, (if you do not want to
use ZFS...)
is it THAT a problem to wait 5-10 minutes for fsck?
on OS that really crash RARELY. Most cases not at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.fr
Hello,
try to use journaling on the backup partition, (if you do not want to
use ZFS...)
than: supose your partition is ad0s1d,
this procedure will destroy ALL data on the partition!!!
gjournal load
gjournal label ad0s1d
newfs ad0s1d.journal
edit the /etc/fstab to look like:
/dev/ad0s1d.journa
Wojciech Puchar wrote:
my 6 disk system with 2 750GB disks, 2 500GB disks and 2 320GB disks
does fsck in 40 minutes. if you exclude these 320GB disk containing
system and squid cache (LOTS of files) it takes <5 minutes
That's a great example of why I like ZFS on new installations.
--
Kirk Str
I just installed 7.2 on a 1.5TB RAID 5. I'm using about 10GB for the
system and swap, and the rest for a single large partition to be used for
backups. As of right now, the single partition, /bkup, is empty.
Some will disagree, but this almost screams for ZFS: no fsck, great RAID
support, and
John Nielsen. wrote:
I just installed 7.2 on a 1.5TB RAID 5. I'm using about 10GB for the
system and swap, and the rest for a single large partition to be used for
backups. As of right now, the single partition, /bkup, is empty.
Some will disagree, but this almost screams for ZFS: no fsck, gr
system and swap, and the rest for a single large partition to be used for
backups. As of right now, the single partition, /bkup, is empty.
When booting after an improper shutdown, the system starts the backgrounds
fsck as usual and on all the other partitions, seem to take the "normal"
turn of
Hey guys...
I just installed 7.2 on a 1.5TB RAID 5. I'm using about 10GB for the
system and swap, and the rest for a single large partition to be used for
backups. As of right now, the single partition, /bkup, is empty.
When booting after an improper shutdown, the system starts the backgrounds
f