On Sun, Oct 18, 2009 at 12:25:22PM +0530, Ritesh Raj Sarraf wrote: > On Sunday 18 Oct 2009 12:00:36 Alex Samad wrote: > > my uncompressed directory is /backups/.max, it is fusemounted to > > /backusp/max. > > > > the file /backups/max/max/alex.zip is being compressed - when I check > > /backups/.max/max/alex.zip it is being compressed. > > > > where as a file /backups/max/max/alex.bz2 doesn't get compressed > > > > > bzip2 is a high compression algorithm. It could just be that there is no room > for compression anymore.
some file type (based my mime type) are meant to be excluded from the compression and zip is meant to be one of them. plus the difference the bzip2 file went through with out being touched where as the zip did not and ended up being larger then before if you run fusecompress it shows you the list of files that are not meant to be touched application/x-zip is one of them > > > such that unzip -l /backups/max/max/alex.zip works and unzip -l > > /backups/.max/max/alex.zip fails with corrupted file > > > Again, aren't you supposed to be accessing the data only through a > fusecompress mounted mount point ? I was testing this when I was looking at the fusecompress_offline which can work with the normal fs. I am presuming the magic sequence is so that you can identify which files have been compressed from the man page fusecompress_offline - decompress or compress data without need to mount the compressed virtual filesystem > > Ritesh
signature.asc
Description: Digital signature
