similar to: About Names

There's a new set of ext2/3 patches for 2.4.21-pre5 available at: http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21pre5-2 and in broken out form at: http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21pre5-2 New to this patch set include: * A kludge to help htree work well with Linux's NFS implementation * Allow the orlov allocator to be disabled via a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 13:05, Rick Sivernell babbled: > Doug > > Educate me please. What is the diff between ext2 & 3. I am using reiserfs > now and do like it. But I do like to have the stuff going, if I can. Be warned, I know nothing about reiserfs other than what I've read. short version: ext3 is a further development of

Hi, Newbie question here. I've read some about how you can't power down a disk under ext3 because of the journaling writes. I also know I can mount my ext3 partitions as ext2. What about mounting the partitions as ext2 while mobile on batteries? The hard disk would spin down when it wasn't in use (if noflush, etc. has been configured). But what about data integrity when

Optimizations by reducing the STREQ operations and do some code cleanup. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/mkfs.c | 29 +++++++++++++---------------- 1 files changed, 13 insertions(+), 16 deletions(-) diff --git a/daemon/mkfs.c b/daemon/mkfs.c index a2c2366..7757623 100644 --- a/daemon/mkfs.c +++ b/daemon/mkfs.c @@ -44,13 +44,16 @@ do_mkfs_opts (const

Hello, I'm creating a large ext3 filesystem on an LVM volume, on top of a RAID1 for storing Norton Ghost disk images. Most of the files created will be between 1 and 10 GB; there may also be occasional small files also. I'm already going to reduce the number of inodes on the filesystem. Probably limit it to 102400 or so. `mke2fs --help` reports a "-g blocks_per_group" option,

Hi, I just converted all my hard disk filesystems from ext2 to ext3. This worked perfectly fine for all non-root fs, but I am having trouble converting the root fs, too. Here's what I did: 1. rebuilt my kernel (2.4.20, x86) with ext3 support linked in statically - no module. 2. Added a journal file to my root fs using 'tune2fs -j'. 3. Added 'rootfstype=ext3' to the

Can anyone comment on whether or not it is possible to successfully disable the journal of an ext3 root file system prior to reboot? My application is to try and make sure there is no journal prior to installing and rebooting into a system which does not support ext3. I know that as long as the root is cleanly remounted r/o with no journal updates pending, this will be compatible. I'm

> Hi, > Sorry if this is a stupid question (bit of a newbie). I'm building a Samba > fileserver on a box with a hardware raid array of about 65GB which I'm > hoping to share out to the local LAN . I was wondering if the filesystem > used (ext2,ext3, reiserfs etc) on the partition where the Samba shares > will reside makes much of a difference? I'd obviously like to

Add the 'label' optional argument to the mkfs action, so it is possible to set a filesystem label direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just

I run a decent amount of 3ware hardware, all under centos-4. There seems to be some sort of fundamental disagreement between ext3 and 3ware's hardware RAID5 mode that trashes write performance. As a representative example, one current setup is 2 9550SX-12 boards in hardware RAID5 mode (256KB stripe size) with a software RAID0 stripe on top (also 256KB chunks). bonnie++ results look

According to this: http://www.redhat.com/support/wpapers/redhat/ext3/why.html ext3 is forward and backward compatible with ext2... Any user who wishes to un-journal a file system can do so easily... I am assuming un-journalling is the equivalent of converting it to ext2. How do you do this? I haven't been able to find anything. The reason I want to do this is so I can modify my

Hi, I am using ext3 file system. Can I know the place where journal log is stored and more details about journaling. Quick response is appreciated. Thanks in advance, Mallika. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20041227/574c90bf/attachment.htm>

Hi, I tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

Hi, This is probably way far unsupported, but here goes: I had been running ext3 0.0.3b for a while and found that I wanted to convert back to ext2 so I could still play with 2.4test kernels. Here is what I did: 1) boot the machine with kernel args init=/bin/bash 2) run debugfs on the root partition to remove the have_journal ext2 feature flag. 3) remount the root filesystem rw as ext2

Everyone, We just had a pretty bad crash on one of production boxes and the ext2 filesystem on the data partition of our box had some major filesystem corruption. Needless to say, I am now looking into converting the filesystem to ext3 and I have some questions regarding ext3 and Linux software RAID. I have read that previously there were some issues running ext3 on a software raid device

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

hi i got 2 questions and maybe someone could shed some light: a) i'm using kernel 2.4.17 and use ext3 in it. is it possible that the whole system is slower than with ext2? i switched back to ext2 (great feature!!!) and the system's response seemed somewhat better. should/could there be such a effect as double writing of journaled data? i didnt activate debugging (jbd). b) is reiserfs

When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for

Dear Listmembers, I try to work with samba (newest rpm for SuSE, 3.0.1.pre2, but that does not matter, the effect was there in 2.2.7 and 2.2.8a too) on an sufficient armed system (the system does not matter either, I have tried it on different machines) using ReiserFS (version 3.6.4-12). When accessing one share from one machine (i.e. copying two or more files at a time to or from the share)

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > 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 >