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.
<br><br><div><span class="gmail_quote">On 7/21/07, <b class="gmail_sendername">Hal Duston</b> <<a href="mailto:hald@kc.rr.com">hald@kc.rr.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sat, Jul 21, 2007 at 09:58:03AM -0500, Billy Crook wrote:<br>> I just rsynced everything on one fs to another of the same type and size.<br>> Both underlying disks arw partitioned the same, and of the same model<br>
> number. What could be causing this discrepancy in availiable space?<br>><br>> [BCrook@Desktop1 ~]$ df -h<br>> Filesystem Size Used Avail Use% Mounted on<br>> ....<br>> /dev/mapper/crypt 688G 561G 120G 83% /mnt/crypt
<br>> /dev/mapper/crypt2 688G 561G 92G 86% /mnt/crypt2<br>> [BCrook@Desktop1 ~]$ mount<br>> .....<br>> /dev/mapper/crypt on /mnt/crypt type ext3 (rw)<br>> /dev/mapper/crypt2 on /mnt/crypt2 type ext3 (rw)
<br><br>Check the reserved block count. This is the count of filesystem<br>blocks reserved for the super-user.<br><br>tune2fs -l /dev/mapper/crypt<br>tune2fs -l /dev/mapper/crypt2<br><br>or<br><br>dumpe2fs -h /dev/mapper/crypt
<br>dumpe2fs -h /dev/mapper/crypt2<br><br>At a guess, I'd say that crypt has a reserve of 0%, and crypt2 has a<br>reserve of 5%, which is the mke2fs default.<br><br>--<br>Hal Duston<br><a href="mailto:hald@kc.rr.com">
hald@kc.rr.com</a><br>_______________________________________________<br>Kclug mailing list<br><a href="mailto:Kclug@kclug.org">Kclug@kclug.org</a><br><a href="http://kclug.org/mailman/listinfo/kclug">http://kclug.org/mailman/listinfo/kclug
</a><br></blockquote></div><br>