similar to: Ordered vs. journal real-worl performance

Hi, I'd like to use a flash drive as a journal device, with the purpose of keeping the main disk drive spun down as long as possible. I have a couple of questions: 1) Does the journaling code spread write accesses to the journal device evenly, as I hope, or are there blocks that are particularly "hot"? I.e., do I have to worry about the flash device dying quickly because of

I'm lacking some understanding of how to tune / when to tune /proc/sys/vm/bdflush Where can I read up on this? Our current problem: Load is low, but ever so often the system decides to do some serious disk I/O which causes all processes to wait for disk I/O -- load explodes (rises linear up into the 20-30ies) just to fall linearly (spelling?) right after that. We think there might be some

Hi, I installed World of Warcraft on Wine, but I have a problem, World of Warcraft works very slow, and is impossible to play. Some time ago I tried World of Warcraft on Wine, when used Ubuntu and works great, but now works very slow. Wine version: 1.3.25 O.S.: ArchLinux 64 bits with desktop environment Gnome 3. Graphics: Mobile Intel GM45 Express Chipset Integrated Graphics CPU: Pentium(R)

Hi, I don´t think that this is a ext3 Problem, since you have problems partitioning that disk. Perhaps a hdparm -i /dev/hdX could shine some light on this, also a fdisk -l /dev/hdX could be useful. For now - let me guess: <guess> To me, it seems, that the disk is clipped to 32GB, perhaps the mainboard bios can not cope with a disk >32GB - just a thought. Since the manufactorer

Greetings all, I have a question regarding the fsync data corruption bug that was introduced in 2.4.20 when using data=journal. I have patched the 2.4.20 kernel with the 3 sync patches available from zip.com.au, and I am wondering if with these patches the "bug" still exists: sync_fs.patch sync_fs-fix.patch sync_fs-fix-2.patch In addition the following two patches have also

Quoting Alexander Dalloz <ad+lists at uni-x.org>: > Am 23.07.2017 um 17:50 schrieb david.madman2 at vfemail.net: >> My /var/log/mail.log shows: >> >> Jul 22 18:40:48 www dovecot: auth: Error: >> passwd-file(test at domain.com,46.xxx.xxx.xxx,<wZoHUuxU6IAu9j4y>): >> Password data is not valid for scheme SHA256: Input length isn't >> valid

I'm trying to eek every last bit of performance out of a sync NFS server using ext3. I created a 400MB journal, for my data=journal disk. When copying a 200MB file to the machine, by the sound of the disk, it flushed data to disk about 4 times, so, about every 50MB. For the purposes of user experience, it would be great if this could be tuned. I'd set it to just over a couple

I have a heavily loaded Apache 2 server which is experiencing what appear to be "write storms". The server is a dual Xeon box with hyperthreading, and appears to linux as a four-cpu box. It has 4GB of physical RAM and is never hitting swap. It's serving a large number of static image files off of four 135GB SCSI drives with external journals on a fifth volume. The journal volume

Hi, as I mentioned in earlier mail to ext3-users I have been getting some corruption on an ext3 filesystem that has been serving NFS. I am now confident that I fully understand the problem and have a patch. It only affects data=journal mode and I wonder if it might also be the cause of the corruption noted by a number of people on linux-kernel. First I will explain the problem. Then display

A scsi error (caused possibly by a loose cable) has left the processes accessing my ext3 file system hung in an unkillable state after it triggered an assert in ext3's journaling layer. I assume my only recourse at this point is to reboot. Please correct me if I'm wrong. Log messages appended. Thanks, -Jim Nov 21 04:04:04 attila kernel: SCSI disk error : host 0 channel 0 id 5 lun 0

Hello, We found that fsync and fdatasync syscalls sometimes don't sync data in an ext3 file system under the following conditions. 1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2). 2. Ext3's journalling mode is "data=journal". 3. Create a file (whose size is 1Mbytes) and execute umount/mount. 4. lseek to a random position within the file, write 8192 bytes

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest initrd thanks I see that this bug is still present in pkg-xen svn: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file Perhaps I wasn?t clear how severe this problem is. Using the current Debianized xen-utils-unstable, it is impossible to boot any

Does anyone know of any Linux-based filesystem that does file-level auditing and logs based on username? Does ext2/3 do such auditing (stock or with patches)? I would like a filesystem that can be told to audit and log file deletions and log the username that deleted the file (similar to auditing on NTFS). I know, I should be using file permissions to prevent this type of deletion from

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

Hi all, Sorry to post OT but I'm a bit stuck and I thought someone may know the answer. Originally I installed Red Hat 5.2 with 2 paritions, boot and root. I upgraded to Red Hat 6 (kept the original filesystem) without a problem some time ago, but now I want to upgrade to 7.2. When trying to install the upgrade it tells me that the boot parition isnt big enough (by about 90k!) so I thought

Our Invoice posting routine (intensive harddrive io) freezes every few seconds to flush the cache. Reading this: https://listman.redhat.com/archives/ext3-users/2002-November/msg00070.html I decided to try: # elvtune -r 2048 -w 131072 /dev/sda # echo "90 500 0 0 600000 600000 95 20 0" >/proc/sys/vm/bdflush # run_post_routine # elvtune -r 128 -w 512 /dev/sda # echo "30 500 0 0

I apologize if this is off-topic, because I'm not sure if /proc/sys/vm/bdflush has anything to do with ext3 performance or not. However, I've been searching around for a while and can't find the answer I need. If somebody could shed some light, I'd really appreciate it. In "Securing and Optimizing Linux: RedHat Edition -A Hands on Guide", the author gives these values to

Get this warning on bootup ext3 file checks on 2.6.* kernels. Apparently harmless, but how do I fix this? _______________________________________________ debian-knoppix mailing list debian-knoppix at linuxtag.org http://mailman.linuxtag.org/mailman/listinfo/debian-knoppix

(Sent to linux-raid, linux-kernel and ext3-users since I'm not sure what type of issue this is) I've got a test system here running Redhat 7.1 + stock 2.4.9 with these patches: http://www.fys.uio.no/~trondmy/src/2.4.9/linux-2.4.9-NFS_ALL.dif http://www.zip.com.au/~akpm/ext3-2.4-0.9.6-249.gz http://domsch.com/linux/aacraid/linux-2.4.9-aacraid-20010816.patch All three patches applied

I have a partition that is formatted as ext3 however, due to apparent performance issues (not sure if they are related to journaling - data=ordered, BTW) I have mounted this file system as ext2. The file system was clean when it was shutdown, and has been cleanly mounted as ext2, and I currently have no problems with the partition. My question is, is there any harm in mounting this partition as