search for: dumpe2f

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

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 their mail file, it is 10493792 bytes, which means they should be using 2...

...&& fdisk -l | grep /dev/sdb3", onlyif => "iscsi-rescan && [ -e /dev/sdb ]", require => Service[''iscsi''] } ... exec { "mke2fs /dev/sdb1": path => ''/sbin'', unless => "dumpe2fs /dev/sdb1", require => Exec["echo -e \"0,290\\n,290\\n,\" | sfdisk /dev/sdb"] } ... exec { "mke2fs /dev/sdb3": path => ''/sbin'', unless => "dumpe2fs /dev/sdb3", require => Exec["e...

...Start (sector) End (sector) Size Code Name 1 34 58593784 27.9 GiB EF00 root part 2 58593785 234375035 83.8 GiB 0700 home part 3 234375036 250069630 7.5 GiB 8200 swap part However, to my surprise, the file(1) and dumpe2fs(8) utilities were still able to show information regarding file system: root at T60:~# file -s /dev/sda1 /dev/sda1: sticky Linux rev 1.0 ext4 filesystem data, UUID=88e70e1b-4c45-4e7e-931f-9e97d7257ee8 (needs journal recovery) (extents) (large files) (huge files) root at T60:~# dumpe2fs /dev/sda1...

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance) joe I have tried several times such as: -:/ # cat /etc/fstab | grep /dev/hda6 /dev/hda6 /...

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

...e 1' to reenable. Give root password for maintenance (or type Control-D to continue): entering 'e2fsck -h 8193 /dev/sda3' results with same e2fsck message as above. after reading article; http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition/ using command; dumpe2fs /dev/sda3 | grep superblock error message is; dumpe2fs: No such file or directory while trying to open /dev/sda3 Couldn't find valid filesystem superblock. if i enter command; dumpe2fs /dev/sde3 | grep superblock superblock info is shown. why is sde working and not sda? this system ha...

Hello, How to upgrade existing ext3 partition to new features? Moved from RHEL3 to RHEL4. I had to install from c0d0p6 so partition could not be reformated during install. Thanks, Mindaugas # dumpe2fs /dev/cciss/c0d0p1 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super # dumpe2fs /dev/cciss/c0d0p6 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal filetype needs_...

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,

...n 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 utility do not provide timestamp of each allocated inode and I am thinking of modifying source code of e2fsprogs. My two questions are: 1. Is it correct to use "dumpe2fs" program and modify for timestamp ? 2. I could not understand the main purpose of e2fsprogs....

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

OK. Thanks for the journal information. I thought tune2fs -l and dumpe2fs were the same. In reality it's almost the same but not entirely ^^ I hear you about all the internal mecanisms that make the FS working or give it some features, and I do understand that it takes some place on the disk. However what I don't understand is why the number given in the "...

...or group 127 is not in group. (block 0) Relocate? yes Inode table for group 127 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes fsck.ext2: e2fsck_read_bitmaps: illegal bitmap block(s) for /dev/hda4 dd if=/dev/hda of=/dev/sda conv=noerror,sync dumpe2fs /dev/sda4 dumpe2fs 1.35 (28-Feb-2004) ext2fs_read_bb_inode: Invalid argument Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: a300ff1d-5cf0-4d8a-9336-ae39bc64ed95 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic)...

...e i gave above is just a example and there are many more files like this. Also only 10% of the files have different sizes. I.e out of 263032 files/folders only 17655 have the above problem. Below is the ext3 filesystem info on both the master and failover. [root at storage-master repositories]# dumpe2fs -h /dev/sda1 dumpe2fs 1.35 (28-Feb-2004) Filesystem volume name: /store1 Last mounted on: <not available> Filesystem UUID: 2368a03d-f21f-4c5e-b12a-cbd2c726237c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext...

...ed if the file system syncfs(2) or sync(2) system call. But if you crash, any writes since the last syncfs(2), sync(2), or umount(2) call on the file system can get lost, yes. > Also the value is only available in granularity of 1 GB (plus minus > 512MB) - at least in my case. This is what dumpe2fs is currently using: if (sb->s_kbytes_written) { fprintf(f, "Lifetime writes: "); if (sb->s_kbytes_written < POW2(13)) fprintf(f, "%llu kB\n", sb->s_kbytes_written); else if (sb->s_kbytes_written < POW2(23)) fprintf(f, "%llu MB\n&quo...

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

...uot;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?) # dumpe2fs /dev/$YOUR_DEVICE | grep Journal dumpe2fs 1.41.12 (17-May-2010) Journal inode: 8 Journal backup: inode blocks Journal features: journal_incompat_revoke Journal size: 128M Journal length: 32768 But you also need to take into account inode tables,...

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;

Hi all, I'm looking for a tool that lists the used blocks in an ext3 file system. Is there already a tool that does exactly that? The closest I could find is dumpe2fs which lists groups, and free blocks within the group. Thanks, -Samson

...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 doesn't seem to know about it: Filesystem features: filetype sparse_super What to do?