similar to: Extended Attribute Write Performance

On Tue, Feb 18, 2020 at 01:18:54PM +0200, Nikolay Ivanets wrote: > вт, 18 лют. 2020 о 10:48 Richard W.M. Jones <rjones@redhat.com> пише: > > > > When calculating the initial size of the disk we must estimate > > how much space is taken by the input. This is quite difficult. > > > > For directories we used ‘du --apparent-size -bs DIR’. This is wrong >

Hello-- We have a system where a central server formats removable hard disks, which are then booted in an embedded system running a highly modified RH9. The removable disks themselves contain boot, root, and data filesystems. The problem we've encountered after upgrading to FC3 / kernel 2.6 on the central server is that the 2.4 kernel in the embedded system cannot read the root filesystem,

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

Hello, I have today released an initial version of extended attributes and access control lists for ext3 (patch against the 2.4.13-ac3 kernel). Eric Jarman <ejarman@acm.org> has contributed a lot to this effort. Since I'm not very much into the innards of ext3, can some of you please take a look at the patch, and see whether it contains any flaws (and tell me which flaws)? Thanks! The

Hi, I noticed that some of my ext3 partitions have a lost+found directory and some do not. Which is correct? mke2fs -j makes the lost+found but after a fresh install of 7.2 there are no lost+found on partitions that were formatted. I want to make them all the same but I am not sure which is correct. I do not plan on going back to ext2 but......... -- ......Tom Dysfunction The Only Consistent

Hello, seems like the new default ext2/ext3 256 bytes inode size problem applies to extlinux. HPA, could you confirm it? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491076 http://e2fsprogs.sourceforge.net/e2fsprogs-release.html E2fsprogs 1.40.5 (January 27, 2008) "Mke2fs will now create new filesystems with 256 byte inodes and the ext_attr feature flag by default. This allows for

Hi list this is actually a problem on a debian system but I thought you might be interested to hear of it and perhaps can offer some help. I have a woody box (dell pe750, dual cpu) running a kernel from backports.org (debian 'testing' packages built on a 'stable' box). The kernel version is 2.6.7-1.backports.org.1. This host is hooked up to an Apple Xserve RAID with a 2.3Tbyte

Hello, I am the guy behind the ext2/ext3 patches for Extended Attributes and ACLs, and I've recently been asked about ACL support in rsync by Eric. Upon investigating I found that you have an ACL patch against rsync-2.5.5 [1]. I also found some other postings to rsync@lists.samba.org concerning rsync and ACLs [3]. Are there any plans for finalizing an integrating that rsync ACL patch? I

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

Hi. I'm attempting to setup a box here to be a file-server for all my data. I'm attempting to resize an ext3 partition to demonstrate this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

Hi, Suppose you have an ext2 Partition at 14GB which is 80-90% full. Most files are smaller than 1 MB (there are just 20 or so which are over 100MB where 800MB is the biggest one). Block size etc - everything is default. Now you do this: mke2fs -j /device Important is the "-j" switch. What happens without the "-j" switch? All superblocks and inodes are overwritten. Is this

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Is there a way to create an ext3 filesystem (such as mke2fs will create an ext2 filesystem)? Is there a way to convert a vfat or ext2 filesystem to ext3? Thanks! SJR

Hi, I'm working with Prof. Zadok on versionfs, a stackable versioning file system. I face some problems with the unlink operation on ext3 with htree. On an unlink, I make a copy of the file (version/backup) and unlink the original file. But some files that have been unlinked are "linked back" to another file. For example, on deleting the file 'foo', the file itself is

I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.

Good day, some time ago we discussed that it would be very helpful to store epoch in inode on mds. the perfect solution could be to store epoch in old inode body, but there is no much space for this in the body and with DMU we''ll have this problem again. given the minimal inode size we use on MDS is 512 bytes, we can store upto 13 stripes in the body. larger EAs go to a dedicated block.

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and