similar to: ext3 compatibility between 2.4 and 2.6 kernels

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

Documentation/ext3.txt suggests that the "user_xattr" and "acl" mount options are on by default. This doesn't seem to be the case, as the kernel deduces the default mount options from the filesystem superblock, and mke2fs does not appear to write any default mount options there. This error was spotted by Jacques de Mer. Signed-off-by: Daniel Drake <dsd at

Hello everybody, I am new to this list, so welcome everybody. Last 2 week I had two harddisk crashes with my ext2 file system. This is what sort of happed with both of the disk: I pluged in my USB to SATA converter in my harddisk that has an ext2 filesystem. I mounted the partition, went to a directory that had a DVD image. I mounted the dvd image in the same directory and started watching the

On a customer's machine running SuSE 9.2, the size of the occupied space on the harddisk is reported incorrectly by "df -h". After we noticed the problem, I rebooted the machine and had it checked by "e2fsck" (check forced with "tune2fs -C 40", we are not on location). Right after the reboot I proceeded as follows, but I could not find any information about

Hi All: Is there a utility available that will allow for the dump/display of the bad track table of a SCSI drive. We had this capability on SCO OSR5 but I have not been able to locate anything similar for Linux. The closest I have found is the badblocks utility that is part of the e2fsprogs package but this appears to only test for bad blocks not display the current bad block table contents. I

I got the following error, but there''s no "cycle" I commented out File["/dev/sdb3"] and it works, but of course would choke if I ran it and the requirement were not met err: Could not apply complete catalog: Found cycles in the following relationships: File[/dev/sdb1] => Exec[echo -e "0,290\n,290\n," | sfdisk /dev/sdb] Here''s the node: node

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

Hello: I am trying to set up user quotas on my /var partition to enforce limits on user's mailbox sizes. The machine is running CentOS 5. When I do this: /sbin/dumpe2fs /dev/md2 | grep 'Block size' Block size: 4096 That tells me the block size is 4k. But, if I do: repquota /var It is telling me that one of my users is currently using 10264 blocks. But, if I look at

Hi. I was using 2.4.10 with ext3 0.9.10 and thought it was time to use -ac for the first time because 2.4.12-ac3 includes 0.9.12. I don't know what I did to get the following messages, but in my last boot I removed /etc/mtab (at runtime) and made it a symlink to /proc/mounts. Not sure if a bad idea, but the only problem until I rebooted was the need of losetup -d. When I rebooted, all

Hi all, Somehow I managed to mess with a RAID array containing an ext3 partition. Parenthesis, if it matters: I disconnected physically a drive while the array was online. Next thing, I lost the right order of the drives in the array. While trying to re-create it, I overwrote the raid superblocks. Luckily, the array was RAID5 degraded, so whenever I re-created it, it didn't go into sync;

Hello list, I have troubles with the daily backup of a modest filesystem which tends to take more that 10 hours. I have ext4 all over the place on ~200 servers and never ran into such a problem. The filesystem capacity is 300 GB (19,6M inodes) with 196 GB (9,3M inodes) used. It's mounted 'defaults,noatime'. It sits on a hardware RAID array thru plain LVM slices. The RAID array is

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > The "lifetime writes" value has not been around forever, so if the > filesystem was originally created and populated on an older kernel > (e.g. using ext3) it would not contain a record of those writes. It was created as stable ext4 in the first place. So only if there was a stable ext4 release which didn't

On Thu, Oct 16, 2014 at 11:01:35PM +0200, Bodo Thiesen wrote: > > Since it never get's updated unless the file system is unmounted, it can > only be used for a 24 hours test by mounting the file system now, > unmounting it 24 hours from now and then taking the difference. It also gets updated if the file system syncfs(2) or sync(2) system call. But if you crash, any writes since

Hi, I zero-filled first 10MiB of my SSD(dd if=/dev/zero of=/dev/sda bs=10M count=1). As expected, this wiped my primary GPD header and first partition. Before the wipe, GPT was following: Disk /dev/sda: 250069680 sectors, 119.2 GiB Logical sector size: 512 bytes Disk identifier (GUID): 2EFD285D-F8E6-4262-B380-232E866AF15C Partition table holds up to 128 entries First usable sector is 34, last

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

On 9/16/13 9:44 AM, Nicolas Michel wrote: > Thanks for you help. I also tried adding some other informations as you suggest: > I can also take into account: > - "Reserved block count: XXXXXXX" from tune2fs that gives me the > number of blocks reserved for root > - Reserved GDT blocks: XXX > > But I didn't thought about the FS journal. How can I gather

Hello, Hope you will forgive me for asking some very simple question about e2fsprogs. I am very new to the kernel as well as file system programming. My task is to collect superblock, inode, bitmap ( or free list) information from ext2/ext3 filesysteam. After searching the google, I came to know about e2fsprogs, which I was able to install and use at least "dumpe2fs" utility. This

Thanks for you help. I also tried adding some other informations as you suggest: I can also take into account: - "Reserved block count: XXXXXXX" from tune2fs that gives me the number of blocks reserved for root - Reserved GDT blocks: XXX But I didn't thought about the FS journal. How can I gather information about it? (it's size and any other information?) 2013/9/16

Something bad must have happened when I first ran e2fstune on my root file system. Now I cannot mount it ext3 and when I try to run tune2fs -j on it, I get this error message: permission denied while trying to create journal file There is a .journal file in /: [root@monster log]# ls -l /.journal -rw------- 1 root root 33554432 Sep 29 10:21 /.journal But dumpe2fs