From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: the compressed file attribute Date: 29 Jan 2004 15:35:09 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1075415709.2575.80.camel@patibmrh9> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:35287 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S266458AbUA2WgV (ORCPT ); Thu, 29 Jan 2004 17:36:21 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 2B86A28CF for ; Thu, 29 Jan 2004 15:36:20 -0700 (MST) To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Does one of the Linux fs, other than ntfs, already let me distinguish one file from another by a compressed attribute? What I'm hoping to find is: Uncompressed files work same as always. Compressed files appear to work same as always, but under the covers the data of the file occupies more or less space according to how compressible it is. Random access within the file either sequentially rewrites all the file or else garbage collects and defragments. I ask here because I think Google mostly points me to file systems that compress all files e.g. fs/cramfs/README Future Development doesn't mention this twist, e.g. `ls fs | egrep -i nw5` is empty, ... Compressing all files is not the same thing. I don't want the file system deciding for me which files to compress. Pat LaVarre