[lustre-discuss] wildly inaccurate file size

[Carlson, Timothy S]

Is this a ZFS backed Lustre with compression? If so, then that is not at all surprising if that is a compressible file. I have a 1G file of zeros that shows up as 512 bytes

[root at pic-admin03 tim]# ls -sh 1G
512 1G
[root at pic-admin03 tim]# ls -l 1G
-rw-r--r-- 1 tim users 1073741824 Dec  2  2015 1G

-----Original Message-----
From: lustre-discuss [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of John White
Sent: Thursday, June 30, 2016 3:15 PM
To: lustre-discuss at lists.lustre.org
Subject: [lustre-discuss] wildly inaccurate file size

So I’ve got this file that’s really making a file copy tool quite upset.  Would the following point to metadata corruption? I’ve found several files similar to this.

Please note I killed the ‘dd’ after confirming it passed the 189MB mark:

[root at n0001 ~]# dd if=/global/scratch/kclosser/qcscratch/CH3Cl_0_160623-131335.scr.0/73.0 of=/dev/null bs=1024k
^C23131+0 records in
23130+0 records out
24253562880 bytes (24 GB) copied, 22.1161 s, 1.1 GB/s

[root at n0001 ~]# stat /global/scratch/kclosser/qcscratch/CH3Cl_0_160623-131335.scr.0/73.0
  File: `/global/scratch/kclosser/qcscratch/CH3Cl_0_160623-131335.scr.0/73.0'
  Size: 2577009477120	Blocks: 385776     IO Block: 4194304 regular file
Device: 323d03b2h/842859442d	Inode: 148006512164371012  Links: 1
Access: (0644/-rw-r--r--)  Uid: (42015/kclosser)   Gid: (  505/     msd)
Access: 2016-06-30 15:12:57.000000000 -0700
Modify: 2016-06-23 21:33:36.000000000 -0700
Change: 2016-06-23 21:33:36.000000000 -0700
[root at n0001 ~]# ls -sh /global/scratch/kclosser/qcscratch/CH3Cl_0_160623-131335.scr.0/73.0
189M /global/scratch/kclosser/qcscratch/CH3Cl_0_160623-131335.scr.0/73.0
[root at n0001 ~]# 
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org