That must be exactly it. I remember when I formatted crypt, I did specifiy options. Whereas when I formatted crypt2, I did not. Can't check to make sure though. crypt2 will be in a bank vault for 6 months. Crypt3 is in the works though. Should be ready to play with by next Friday. Im just glad it wasn't a filesystem error.
On 7/21/07, Hal Duston <hald@kc.rr.com> wrote:
On Sat, Jul 21, 2007 at 09:58:03AM -0500, Billy Crook wrote:
> I just rsynced everything on one fs to another of the same type and size.
> Both underlying disks arw partitioned the same, and of the same model
> number. What could be causing this discrepancy in availiable space?
>
> [BCrook@Desktop1 ~]$ df -h
> Filesystem Size Used Avail Use% Mounted on
> ....
> /dev/mapper/crypt 688G 561G 120G 83% /mnt/crypt
> /dev/mapper/crypt2 688G 561G 92G 86% /mnt/crypt2
> [BCrook@Desktop1 ~]$ mount
> .....
> /dev/mapper/crypt on /mnt/crypt type ext3 (rw)
> /dev/mapper/crypt2 on /mnt/crypt2 type ext3 (rw)
Check the reserved block count. This is the count of filesystem
blocks reserved for the super-user.
tune2fs -l /dev/mapper/crypt
tune2fs -l /dev/mapper/crypt2
or
dumpe2fs -h /dev/mapper/crypt
dumpe2fs -h /dev/mapper/crypt2
At a guess, I'd say that crypt has a reserve of 0%, and crypt2 has a
reserve of 5%, which is the mke2fs default.
--
Hal Duston
hald@kc.rr.com
_______________________________________________
Kclug mailing list
Kclug@kclug.org
http://kclug.org/mailman/listinfo/kclug