- Journal config for SAN array
- Unlink performance
- e2fsck discrepancies
- see current superblock information
- see current superblock information
- e2fsck discrepancies
- e2fsck discrepancies
- System crash during mke2fs
- System crash during mke2fs
- Undeletable files
- Block bitmap differences
- ext3 file system I/O blocks until reboot
- recovering failed resize2fs
- recovering failed resize2fs
- Need help recovering files.
- How are 'files with holes' stored?
- Backup Superblocks
- giis file undelete tool-new features
- init_special_inode: bogus i_mode
- ext3 zerofree option and RedHat back port?
- badblocks output format question
- Rsync --link-dest and ext3: can I increase the number of inodes?
- Rsync --link-dest and ext3: can I increase the number of inodes?
- directorys
- When is a block free?
- pthread?
- journal on an ssd
- tune2fs
- tune2fs
- Thorsten Henrici ist außer Haus.
- dynamic inode allocation
- dynamic inode allocation
- Problem in HTREE directory node
- ext2online with 1k blocks not working
- ext2online with 1k blocks not working
- small blocks
- duplicate entries on ext3 when using readdir/readdir64
- non-contiguous Inodes
- File permission getting read only
- e2fsck message "inode is too big"
- ext3 filesystem --> read-only
- debugfs question: What does "expand" do?
- fsck.ext3 questions
- ext3 filesystem becomes read-only
- What used to be a directory is now a 0 length file - recovery possible?
- sharp increase in 'used' blocks after plain fs copy
- aborted journal and kernel bug on RHEL AP 5.1 on SUN AMD 64bit (X4200M2)
- aborted journal and kernel bug on RHEL AP 5.1 on SUN AMD 64bit (X4200M2)
- Ext3 problem
- Nanosecond date resolution
- max fs size with 1k blocks
- debugfs question
- inode and filesystem question
- Recommended number of files stored under a single folder
- "Attempt to access beyond end of device" problem
- stride (fwd)
- indexing symbolic links
- stride
- Poor Performance WhenNumber of Files > 1M
- Poor Performance WhenNumber of Files > 1M
- 2GB memory limit running fsck on a +6TB device
- spd_readdir.c and readdir_r
- Fwd: md_thread and kjournald race w/ raid1 on 2-way x86
- Find and delete 'broken files/inodes' in ext3
- Find and delete "broken files/inodes" in ext3
- HTREE corruption
- needs help, root inode gone after usb bus reset on sata disks
- spd_readdir progress report/questions
- ext3_dx_add_entry: Directory index full!
- Extended permissions on ext3
- LD_PRELOAD library to speed directory traversal
- Best Practices for recovering corrupt ext2/3 filesystems
- Functionalities of some functions
- ext3 limits?
- Assertion failure at commit.c: J_ASSERT_JH(h, commit_transaction != cp_transaction)
- EXT3 and SAN Snap Shot, Best practice?
- PATCH bz 442098
- wipe freespace on ext3?
- What can I do to speed up my file system copy
- copying
- Extremely long FSCK. (>24 hours)
- Error compiling on Cent OS 4
- Shrink ext3 filesystem , running out of inode questions
- allocation
- with dir_index ls is slower than without?
- RFC: Search and load drivers automatically fromusb-storage media
- "Write once only but read many" filesystem
- Unable to change the 'name' field from 'ext3_dir_entry_2' structure.
- Unable to change the 'name' field from 'ext3_dir_entry_2' structure.
- memory usage and stage2= ??
- How to get device name with device id?
- The maximum number of files under a folder
- Thank Goodness For The "rescue" Command in GNU Parted
- problems with ext3 after resizing
- giis 4.2 - file undelete tool
- exthide - Linux File hiding tool
- How to read group descriptor?
- Ext3 Repair
- forced fsck (again?)
- Checksumming layer
- root inode corrupted; tries to clear and reallocate, but can't
- How to flush file system buffers?
- ext3 filesystem is not recognized
- read() on a deleted file
- ext3 peformance problem
- lockdep warning with LTP dio test (v2.6.24-rc6-125-g5356f66)
- PROBLEM: Duplicated entries in large NFS shared directory
- Ext3 Performance Tuning - the journal
- Ancient Very slow directory traversal thread
- Meta-data in Ext3
- fsck
- File System Traces
- Proper alignment between disk HW blocks, mdadm strides, and ext[23] blocks