Re: fsck on 1.5TB drive
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 softupdates guarrantes the right sequence of disk updates. For example it will not allocate just freed space until freeid inodes/blocks are not wrote back to disk. As in your example - extended and written something, but will end unextended etc.. by using zfs or journaling I never have anothter database problem This is sequence problem - for example you write to file A,B and C then it's a crash and you have file A and C written but not B. I though that all this famous database systems like mysql already have mechanism for that. looks like not, or it should not get corrupted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
fsck on 1.5TB drive
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 fsck as usual and on all the other partitions, seem to take the normal amount of time. When it gets to the dirty /bkup however, fsck takes about 30 minutes - on an empty partition. On top of that, running a df shows that as much as 2GB of the partition is in use. There's a .snap directory off /bkup, but I can't ls it without the shell hanging. Is this normal behavior? Why is the fsck taking so long on an empty drive? What's the .snap dir for since I haven't run any dumps? Disk access on the rest of the system seems fine, so it doesn't appear to be an issue with the RAID itself. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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 off background fsck. amount of time. When it gets to the dirty /bkup however, fsck takes about 30 minutes - on an empty partition. On top of that, running a df shows that as much as 2GB of the partition is in use. There's a .snap directory off /bkup, but I can't ls it without the shell hanging. Is this normal behavior? Why is the fsck taking so long on an empty because snapshotting takes so much. and even worse - it doesn't work right at least when i tried in FBSD 6.2. Simply turn it off. BTW your backups are mostly big files or mostly small. make use of newfs options - MUCH less inodes, bigger blocks. Not only fsck is faster, but it's faster in normal use and you get less wasted space. reducing -m make sense too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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, great RAID support, and nearly instant snapshots. You should check into it. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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 nearly instant snapshots. You should check into it. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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 Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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.journal /backupufsrw,async11 if you are using a custom kernel, you must include a line in the /boot/loader.conf geom_journal_load=YES now if your system crashes, it will boot up using the journal in the ad0s1d.journal partition, and will make fsck very fast about 1-2 minutes... Hope It can help, Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on 1.5TB drive
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 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.. by using zfs or journaling I never have anothter database problem People can say it is better to use a no-break in the server, Right again but in my case of about 1000 servers, after 2 years the batteries does not function any more... and I can rely only in the filesystem... a shell script that moves the partition to another HD previously formatted with ZFS (on amd64) or journaling (i386) solves my problem Sérgio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
