similar to: Performance problem with mysql on a 3ware 1+0 raid array

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

Hi, i use an BN4S0 with misdn an asterisk on Linux 2.6.9. The hfcmulti module is loaded with option: type=0x04 protocol=0x2,0x2,0x22,0x2 layermask=0xf,0xf,0xf,0xf and the fourth port is connected to an ISDN PTMP (MSN) port. Call to #72 from S0 (BN port 4) are not accepted from asterisk but why ? Can anyone give me a hint ?? misdn debug messages follows: lib: NEW_CR Ind with l3id:80001

Hello, as far as I understood ext3 will more or less hog a machine when writing away the journal. A customer is having a slowdown every 5 minues for about 30 seconds, the machine becomes more or less unusable. This is an NFS server serving 300 Gigs spread over 2 NFS shares. I'm wondering what would be the best course of action: a) make the journal bigger? b) make the journal smaller?

Hi I was wondering if you ever got better performance out of your Gigabit/IDE/Fc2? I am facing a similar situation. I am running FC2 with Samba 3.x My problem lies in not that I am limited to 10 MBytes per second sustained. I think it's related to this pdflush and how it's buffers are setup. (I have been doing some research and before 2.6 kernels bdflush was the method that was used and

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 want to use lastest version of Shorewall in my fresh debian squeeze instalation, so I follow http://www.shorewall.net/Install.htm#Debian but, modify preferences file was not enough for me, I have to modify/add some other files in /etc/apt/ directory: 1.) include testing repo to source.list 2.) add APT::Default-Release "stable"; to apt.conf and pinning all other packages to stable

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

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 Chris. I think it is needed to call mark_inode_dirty() when file size expands in order to flush metadata updates to HDD through sync() syscall or background_writeout(). Thanks. Signed-off-by: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp> diff -Nrup linux-2.6.29-rc3.org/fs/btrfs/file.c linux-2.6.29-rc3/fs/btrfs/file.c --- linux-2.6.29-rc3.org/fs/btrfs/file.c 2009-02-02

Hi, I am building a firewall that will have two groups of subnets behind it which I''ll provision via vlans. The upstream provider will be supplying a router with a single interface with two subnets routed into it, one is a private connection to the corporate WAN and the other is a public (Internet) block. One group of subnets behind the firewall will be SNAT''d out through a

(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

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

Well.... you might remember that I have had problems will my NFS fileserver that run ext3 with data=journal. The filesystem corruption now seems too be solved with the patch (plus amendment) that I posted, so I am happy about that... but there is more. I have known for a while that ext3 doesn't behave very well when the journal fills up. If it finds that the journal is full, and the

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

Hello all, I''m using shorewall on a linux machine that has two interfaces, eth0 being connected on the internal network (10.10.10.0/24) and eth1 being connected to the external network. On eth0 the IP is statically configured to 10.10.10.254 and there is a dhcp server running for the machines in the private network. On eth1, the IP is dynamically assigned by my ISP modem that acts as

Hi, Got the following on Linux 2.5.37 trying to run apt-get update. MikaL Sep 21 23:10:05 devil kernel: Assertion failure in ext3_get_block() at inode.c:853: "handle != 0" Sep 21 23:10:05 devil kernel: kernel BUG at inode.c:853! Sep 21 23:10:05 devil kernel: invalid operand: 0000 Sep 21 23:10:05 devil kernel: CPU: 1 Sep 21 23:10:05 devil kernel: EIP:

If we race with commit code setting i_transaction to NULL, we could possibly dereference it. Proper locking requires journal pointer (journal->j_list_lock) we don't have. So we have to change the prototype of the function so that filesystem passes us the journal pointer. Also add more detailed comment about why function does what it does how it should be used. Thanks to Dan Carpenter

Hi all, This patchset makes some key modifications to the original ''stable page writes'' patchset. First, it provides users (devices and filesystems) of a backing_dev_info the ability to declare whether or not it is necessary to ensure that page contents cannot change during writeout, whereas the current code assumes that this is true. Second, it relaxes the

================================================================ KVM Forum 2017: Call For Participation October 25-27, 2017 - Hilton Prague - Prague, Czech Republic (All submissions must be received before midnight June 15, 2017) ================================================================= KVM Forum is an annual event that presents a rare opportunity for developers and users to meet,

================================================================ KVM Forum 2017: Call For Participation October 25-27, 2017 - Hilton Prague - Prague, Czech Republic (All submissions must be received before midnight June 15, 2017) ================================================================= KVM Forum is an annual event that presents a rare opportunity for developers and users to meet,