similar to: Ext2/3 and sparse files.

Hi, i have two twofold e2image related questions: 1) The man page mentions "cp (1)"'s --sparse=always option. I wonder if there are sparse aware tools which a) display the "real" amount of disk space occupied by a sparse file b) compress sparse files (other than compressing very thightly several GiB of zeros) 2) "E2fsck, mke2fs, etc.

Question: Does ext2/3 (or any other filesystem you know of) support a system call turning blocks within a file back into "sparse zeros", i.e. giving the blocks back to the filesystem? Background: I am working on a slotted fileformat where internal fragmentation occurs. One such occurrence is growth of the data in a given slot, which currently requires me to handle the

[Jim, as coreutils developer, this might interest you] In libguestfs we run some quite detailed checks of the output of the statvfs system call for our tool "virt-df". I noticed that the output of virt-df changed slightly. Narrowing it down, the difference only happens between: Fedora kernel 3.2.0-0.rc0.git4.1.fc17 (3rd Nov) Fedora kernel 3.2.0-0.rc1.git2.1.fc17 (11th Nov) With

A couple of years ago there was a discussion on lkml under the thread 'PATCH - ext2fs privacy (i.e. secure deletion) patch' about zapping deleted data in the filesystem as a security mechanism. The discussion wandered off into how 'chattr +s' could be implemented and whether encrypting filesystems wouldn't be a better solution to the problem. I've been maintaining a

I'm writing a stackable file system and one of it's features is that it can combine many sparse files into a single view. On ext2/3 I was using bmap to give me the information needed, so for instance, if I created a big sparse file and tacked on some information at the end on ext2/3 I'd get something like blade12:~# ~/a.out abc File: abc Size: 30002 Blocks: 8 Blocksize: 4096 0

Applies on top of my pending series for the exportname filter, addressing one of the todo's in that cover letter. Eric Blake (2): filters: Add .export_description wrappers ext2: Supply .list_exports and .default_export filters/ext2/nbdkit-ext2-filter.pod | 3 +- tests/Makefile.am | 16 +++- filters/ext2/ext2.c | 125 +++++++++++++++++++---------

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

Someone recently posted the following statement midway down the page at http://forums.gentoo.org/viewtopic-t-305871-postdays-0-postorder-asc-highlight-ext3+ordered+data-start-25.html >You don't need to defragment ext2/ext3 because as you use the >filesystem file blocks and inodes are moved around and reallocated >to keep the data nearly contiguous. It's not perfect, but it

The NBD protocol is adding an extension to let servers advertise initialization state to the client: whether the image contains holes, and whether it is known to read as all zeroes. For file-based plugins, we are already probing lseek(SEEK_HOLE) to learn if extents are supported; a slight tweak to remember if that result is EOF tells us if we are sparse, and a similar lseek(SEEK_DATA) returning

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

Hi, I have installed Red Hat Linux 7.3 with ext2 file system and I have multiple partition. I converted them to ext3 using following command. tune2fs -j -i 0 /dev/hdaX And I modified /etc/fstab as below. LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts

hi all I want to know wt does s_log_blocksize represent in ext2's superblock structure in memory.. Is is 1024 for 1kb block size in ext2 file system.. Also wt does s_blocksize and s_blocksize_bits members of VFS superblock represent.. BTW are there any ext2 file system specific mailing lists.. bye a Linux lover

I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules. /etc/mtab reports the filesystem mounted ext3 /proc/mounts reports it mounted ext2 /proc/filesystems lists ext3 If I umount other partitions that are ext3 the module becomes 'unused'. The filesystem was created

I have a partition that is formatted as ext3 however, due to apparent performance issues (not sure if they are related to journaling - data=ordered, BTW) I have mounted this file system as ext2. The file system was clean when it was shutdown, and has been cleanly mounted as ext2, and I currently have no problems with the partition. My question is, is there any harm in mounting this partition as

If I have an image of a filesystem taken with dd, I can look at it with a hex editor and discover that an ext2/3 superblock is at offset 1024 and I can figure out a lot of info about it. I cannot figure out, however, how the superblock differs from ext2 in ext3. I can't tell them apart... the "magic number" is the same as well as the "revision" field. If I have such an

Hi, Also I do have some problems mounting an ext3fs which gets just mounted as an ext2fs. (Yeap, I looked a little bit around in the mailling list and found similiar problems which haven't help me ;-( ) I have a root ( /) and a /mnt partition. both are converted via tune2fs -j into a journaled fs. my fstab looks like this: /dev/hda1 / ext2 defaults

Reading archives I did found letter related to my question: Stephen C. Tweedie: > > On Fri, Jul 20, 2001 at 08:27:44PM +0300, Nikolaos Kefalas wrote: >> I want only to ask , if it is necessary to run tun2fs -J the kernel to have >> support for ext3 . >> I want to boot , from another linux to convert my partions since the partition >> must not be >> mounted

Hi, I just tested ext2 and ext3(2.4-0.9.6) with 2.4.8-ac8, using bonnie++-1.01. The hardware is an old Pentium 100 box with 48M RAM and a 16.6MB/s EIDE harddrive. The test results(see attachment) show ext3 is a lot slower than ext2 in most aspects. Does anybody get better results? Wenzhuo