search for: dumpfs

I am building a tool to identify the file that has a specific LBA. The approach I am using is to search through each inode from number 2 up. This approach works well with UFS1 file systems as then preinitialize all the inodes. However, UFS2 does lazy inode initialization so there are always some that are basically garbage. I have not found any relaiable way to determine from the

.../rescue/[ 5M /rescue/rcp 5M /rescue/csh 5M /rescue/tcsh 5M /rescue/atacontrol 5M /rescue/badsect 5M /rescue/camcontrol 5M /rescue/ccdconfig 5M /rescue/clri 5M /rescue/devfs 5M /rescue/dmesg 5M /rescue/dump 5M /rescue/rdump 5M /rescue/dumpfs 5M /rescue/dumpon 5M /rescue/fsck 5M /rescue/fsck_ffs 5M /rescue/fsck_4.2bsd 5M /rescue/fsck_ufs 5M /rescue/fsck_msdosfs 5M /rescue/fsdb 5M /rescue/fsirand 5M /rescue/gbde 5M /rescue/geom 5M /rescue/glabel 5M /rescue/gpart 5M /rescue/...

...with a block size less than 16k (on the i386 architecture) or 32k (on the alpha architecture), such as those created using the default FFS filesystem block size prior to 4.5-RELEASE, are not vulnerable. The following command can be used to determine the block size used on a given filesystem: # dumpfs /some/filesystem | grep '^bsize' IV. Workaround On filesystems with 16k blocks, the bug cannot be exploited when a process has a file size resource limit (RLIMIT_FSIZE) of 63 MB or less. This can be most easily accomplished by modifying /etc/login.conf so that the appropriate login clas...

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 data out of the disk I'm learning to use the e2fs progs package. Origianlly I used version 1.38, but after experiencing segfaults in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was formatted as ext3, and debugfs / dumpfs showed that the feature 'has_journal' was present (as expected). The e2fsck command gave the following: # e2fsck -B4096 -b32768 /dev/hda11 e2fsck 1.39 (29-May-2006) e2fsck: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /var So it seemed like...

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

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed

<-----------------------------------------------------------------------> Changes to user passwords are captured by a special DLL, which traps and then stores the password changes in encrypted form in a private area. On each synchronization schedule, the synchronization service first examines the SAM file for changes, and then checks this private area for passwords to be synchronized. Once