similar to: (no subject)

I made some tests to see how ext3 reiserfs 3.6 and jfs survive disk errors. The test is simple: format a partition, copy the kernel source, unmount and and do ?dd if=/dev/zero of=/dev/hdd bs=512 count=100000 seek=30000? to simulate a disk surface damage and then run fsck. seek=30000 ? this must be the second half of journal in reiserfs and ext3, for jfs I don't know Result: jfs: ---- total

"IT3 Stuart Blake Tener, USNR-R" wrote: > In terms of enterprise reliability, I understand, however, having an > "office recommended journaling filesystem", Some journaling filesystems can be _worse_ than non-journaled. If the recovery mechanism of the JFS is to "aggressively" go to the journal, journal mis-reads can _toast_ a filesystem. I'll take a full

This patch adds support for swap detection to fstype (to be applied on top of the previous luks patch). The patch is now against klibc's git tree instead of klibc-1.2. Signed-off-by: David H?rdeman <david@2gen.com> -- fstype.c | 42 ++++++++++++++++++++++++++++++------------ swap_fs.h | 18 ++++++++++++++++++ 2 files changed, 48 insertions(+), 12 deletions(-) --------------

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

All, There have been many requests for added kernel features that the upstream provider left out of the standard kernel. (ReiserFS, Video4Linux, Firewire support, XFS, NTFS, JFS, etc.). We want the main release CDs to contain a standard kernel for compatibility and stability reasons. CentOS is created as a clone, and it needs to be as close as possible to the upstream distro. That being said,

Wolfgang, (cc Linux XFS list) (cc Samba list) Quoting wolfgang.glas@ev-i.at: > I just found you message in the samba mailing list archives and foiund > out, that we have a very similar problem. We are using samba-2.2.1a on a > kerenl-2.4.16 and we use reiserfs. > We also experience data corruption with messages like: > > [2002/03/14 15:15:26, 0] >

[ NOTE: I'm putting this off-topic thread back on the Ext3 list, temporarily, as I hope _someone_else_ can help this gentleman better than I have. With each response I get 10 more questions, 5 of them have already been answered and another 5 that utterly confuses me on what he is trying to accomplish, because he's changing his priorities (to often conflicting ones). ] "IT3 Stuart

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appropriately handled. This patchset first

-----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, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM

From: David H?rdeman <david@2gen.com> if a partition has been used as lvm2 and has not been cleared with pvremove, fstype would recognise the ext3 partition as lvm2. workaround that by detection lvm2 after ext3. Bonuspoint remove long fs list as this one just generates conflicts. Signed-off-by: David H?rdeman <david@2gen.com> Signed-off-by: maximilian attems

The attached patch adds support for detecting LUKS partitions (Linux Unified Key Setup - http://luks.endorphin.org/) to fstype. This makes it easier to automatically detect and activate encrypted (root) partitions from an initramfs image. The patch is now against klibc's git tree instead of klibc-1.2. Signed-off-by: David H?rdeman <david@2gen.com> -- fstype.c | 17

The attached patch adds the ability to fstype to detect lvm2 physical volumes (PV's). Signed-off-by: David H?rdeman <david@2gen.com> -------------- next part -------------- diff -Nur klibc-orig/usr/kinit/fstype/fstype.c klibc/usr/kinit/fstype/fstype.c --- klibc-orig/usr/kinit/fstype/fstype.c 2006-03-22 21:28:31.000000000 +0100 +++ klibc/usr/kinit/fstype/fstype.c 2006-03-23

>>>> Fine. Use reiserfs and don't worry about ctime. >>>> >>> But reiserfs doesn´t support ACLs. Does it? >> >> Oh yes, it does. Big way. >> > ?? > > I was under the impression that if i wanted acls, i > should use xfs, ext3 (or jsf i believe) but NOT > reisersf. > > Am I wrong? Does (for example) SuSE 8.2 with >

>> > > Fine. Use reiserfs and don't worry about ctime. >> > >> > Why? Does reiserfs handle ctime in a different >> > way than other linux filesystems? >> >> It's not supposed to given the same instructions >> from clients but it appears to because perhaps it >> elicits different kind of response from Office. >> Maybe

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

I'll try to keep this short (yeah right! ;-). Being primarily a user, I find myself bitching, analyzing and complaining about things I don't stop to understand half the time. I've done more than may share in this regard the various filesystems over the years. I've done a few LUG and tradeshow presentations over the past year, trying to inform different peer admins what Linux JFS

I think I have this one solved, I hope. I think what Andreas and I are running into are a few different assertions. One being the LVM lvm_do_pv_flush caused assertion which is related directly to invalidate_buffers() being called which then triggers refile_buffer() on a journaled buffer, which appears clean in all other ways according to the checks in refile_buffer(). The following is what

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

Hello all, I''ve just installed a new dom0 with openSUSE 11.3 (x86_64) and I''m seeing domUs crashes when reading from disks. The problem occours when in domU configuration I use memory=1024 maxmem=2048 My setup is DRBD on LVM on Software RAID 10 and drbd devices are used as disks for domUs, using phy:/dev/drbd0,hda,w phy:/dev/drbd1,hdb,w The domU in test is HVM, I''m