similar to: data=journal with large external journals

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

Maybe I should've started a new thread with this question (it was in the /proc/sys/vm/bdflush thread), so I am now :) According to tests performed for this article: http://www-106.ibm.com/developerworks/linux/library/l-fs8/ "ext3's data=journal mode is incredibly well-suited to situations where data needs to be read from and written to disk at the same time." This is the

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

I was just trying to build the shared lib stuff and include it into RC4 of FreeAmp 2.1 today, but I found that the .def file for the vorbis build stuff is missing and therefore no .lib file is generated. Is there a reason for that, or is it just an omission? In any case, I will hold off on the latest and greatest vorbis stuff in FreeAmp until next week.... --ruaok Freezerburn! All else

While trying to apply the low-latency kernel patches to our RHv9 Linux 2.4.20-31.9, the patches would not apply. In comparing one of the first patch files (lowlatency.h) to that already on the system, it would appear the low latency patches were already applied by RH. The original RHv9 file (lowlatency.h) even had the patch author's name/credit in it. Does anyone know whether RH made an

Hi! I've spent the last few nights digging into the Vorbis source and working to implement a vorbis_synthesis_pcmout_int() function that kicks out interleaved int16_t pcm data. I think its important to have this function available to make the job for people using the codec a little easier. This function abstracts out the conversion to int16_t and removes the extra overhead of moving the pcm

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

(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

On Wed, 16 Aug 2017 12:46:46 -0700, H. Peter Anvin via Syslinux wrote: >Is that true for vesamenu only, or even for text mode syslinux? Hi, I'm using menu.c32 (text mode only), this is the complete config: [root at archlinux ~]# cat /boot/syslinux/syslinux.cfg # http://syslinux.zytor.com/wiki/index.php/Doc/menu PROMPT 0 TIMEOUT 600 UI menu.c32 MENU HIDDEN MENU CLEAR MENU COLOR screen

Sorry, to interrupt the license flame war... I downloaded the source from CVS as of 11am this morning and there are a couple of issues that I ran into: 1) I built the package and then in the examples dir I executed the following commands: # cdparanoia -B 1-1 # ./encoder-example < track01.cdda.wav > test.vor # ./decoder-example < test.vor > out.wav The rip and the encode both work

Sysctl Values ------------------------------------------- net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 65536 16777216 net.ipv4.tcp_window_scaling = 1 # vm.max-readahead = ? # vm.min-readahead = ? # HW Controler Off # max-readahead = 1024 # min-readahead = 256 # Memory over-commit # vm.overcommit_memory=2 # Memory to

Hello On my HP Compaq dc5800 with Ubuntu 13.04 and their 3.8.0-19-lowlatency kernel, I''ve got quite some kernel traces in the syslog. You can find them below or at http://pastebin.com/bLXPBX67 (to avoid line breaks…). These kernel traces all begin with: WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]() Most of the time, it starts with: Call

I've got a bug pending for FreeAmp right now where the vorbis metadata plugin does not handle international characters right. The comments that are returned from vorbis_comment_query() are in UTF-8, but FreeAmp is ISO 8859-1. I've been looking for a UTF-8 --> ISO 8859-1 converter that is available for inclusion in a GPL/LGPL program and is reasonably small. There are many full blown

BTW, I need a volunteer to upgrade xiph.org to MailMan or the like. I'm officially sick to death of majordomo. (Or, if you want to code all the features I want in majordomo, that's fine too ;-) I'm a little bit out of time, see.... ------- Forwarded Message Sender: robert@emusic.com I just brought the FreeAmp codebase up to speed with the latest Vorbis source. In doing so,

On 10/22/2016 02:06 AM, Nicholas Piggin wrote: > On Fri, 21 Oct 2016 14:05:36 +0200 > Peter Zijlstra <peterz at infradead.org> wrote: > >> On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote: >>> stop_machine can take a very long time if the hypervisor does >>> overcommitment for guest CPUs. When waiting for "the one", lets

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

The beta4 rpms from the vorbis.com site do not install the link to libogg.so.0: lrwxrwxrwx 1 root root 15 Mar 16 18:24 libogg.so.0 -> libogg.so.0.1.0 -rwxr-xr-x 1 root root 16269 Feb 26 04:53 libogg.so.0.1.0 The source dist does it correctly: lrwxrwxrwx 1 root root 15 Feb 27 13:03 libogg.so -> libogg.so.0.1.0 lrwxrwxrwx 1 root root

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'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 having load problems on a server. The bottleneck appears to be disk IO. iostat would show ~100, under %util, during peak usage. i'm running things like clam antivirus, pop, exim, apache, mysql on the server. is there a way to check which process and which file is taking up disk IO? or see what is being written to the disk? i'm very puzzled as the amount of writes is 10 times