[TriLUG] Failure Copying Large Amounts of Data

[Ron Kelley]

Exactly!  From what I understand, large_file provides an inode ratio of "1048576" while normal should provide 4096.  I would rerun the mke2fs command using "mke2fs -j /dev/sdc2" and double-check the inode count.


-Ron



On Apr 16, 2010, at 1:58 PM, boyle at laue.chem.ncsu.edu wrote:

> 
> 
> On 16 Apr, Ron Kelley wrote:
>> That is exactly what I was thinking...
>> 
>> The only thing I can think of - the "mke2fs" command was run with the "-t largefile" 
>> option - which provides much less inodes than a standard "mke2fs" command.
> 
> Both filesystems have the largefile feature enabled.  However, they were
> created several years apart, so the behavior of mke2fs might have
> changed during that time.  Here is dumpe2fs output for the "Filesystem
> features" line:
> 
> A: has_journal filetype needs_recovery sparse_super large_file
> C: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
> 
> Also, the inode size of fs A is 128 while the inode size for C is 256.
> 
> 
> Paul
> 
> 
> -- 
> Paul D. Boyle			    |	boyle at laue.chem.ncsu.edu
> Director, X-ray Structural Facility |	phone: (919) 515-7362
> Department of Chemistry - Box 8204  |	FAX:   (919) 515-8909
> North Carolina State University     |	http://www.xray.ncsu.edu  
> Raleigh, NC, 27695-8204		    |
> PGP Key Fingerprint = D23A 0077 A1BF 277F 8140  FFD2 E4FA 4F99 677D 863E
> -- 
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions