[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/494476 Title: Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/494476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
This is a very serious problem. It's causing unpredictable lockups on my server every 2-3 days, requiring a force-reboot. There are many related reports from other users: e.g. #588046, #667656, #628530, and my particular one, #684654. This bug is not: * Just on server kernels. My kernel is the latest -generic. * File-system specific. Here it's on ext4, mine is on reiserfs, others have reported it on xfs. * A hardware problem, comment #29 notwithstanding. My hardware shows no signs of failure, and too many people are reporting it for it to be caused by simultaneous hardware problems. I hope that someone is going to work on and fix this very soon. Andrew. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/494476 Title: Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi! I vote for a much higher priority too! It's server related and that's why really important. This problem seems caused by high io load. Maybe related only to filesystem io, maybe irq/sec or pure scsi io. I'd be happy to test patches to debug an track this down. Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/494476 Title: Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
My problem was a broken second disk in a raid 1 array. No problems anymore! -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Bad news. After the last update it happened again. I filed a new bug report: bug 652812 Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
If there are no server kernels to test, there should be enough information for the developers to work towards resolving this issue. For all reporters, it would be good to file individual bugs for each system with issues. The bugs can be filed against linux as the package, using ubuntu-bug linux. Please add this bug 494476 to the comments for reference. The individual bugs will give the developers the needed log files and allow them to decide if all of the fixes will be the same. ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged ** Changed in: linux (Ubuntu) Assignee: Surbhi Palande (csurbhi) = (unassigned) -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi there! News! We had no failure since 20 days! This seems to be because we reduced the filesystem usage from 99% down to 70%. This is a XFS filesystem: From: FilesystemSize Used Avail Use% Mounted on /dev/md3 6.1T 6.0T 65G 99% /backup1 /dev/md2 6.1T 5.8T 288G 96% /backup2 To: FilesystemSize Used Avail Use% Mounted on /dev/md3 6.1T 4.2T 1.9T 70% /backup1 /dev/md2 6.1T 1.9T 4.2T 32% /backup2 What about the others? It looks XFS related. Regards. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Any news on this issue? I'm having the same error messages when using tar. Two hours before I was on 8.04: no problems -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, the kernel update from last week has made our troubles worse. I have not managed to get one backup without the 120s blocking since the update. Althout I didn't change anything else. Still using noop as io-scheduler. I'll open a new bug report when no one is responding here. Sorry but this is most important to us. I don't think there is anything special with our hardware or setup: - dual Quad-Core AMD Opteron(tm) Processor 2378 (8 cores) - 32GB Ram - SAS: 08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) 09:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) - SCSI: 02:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev c1) - each SAS serves 24 SATAs HDDs: WDC WD3000HLFS-01G6U1 (Raptor) - SCSI servers HP tape library with two LTO-3 Ultrium 3-SCSI drives best regards Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi! The medium importance might be correct for desktops. Desktops commonly start once per day. But for servers this is most important, because they don't work as expected. Is there someone working on this? Where is the focus for ubuntu: servers or desktops? I'd like to help. But someone has to give instructions. My servers are updated daily. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, bad news. The backup stopped due to timeout. There was no blocking for 120s but there still is some blocking. The probability to happen seems reduced when using noop as io scheduler. Is there someone tracking this down? I'd like to help to get this debugged and resolved. Best regards Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Happening to me too. Several times on the 11th and 12th. May be triggered by load from outside. Looks like a synflood after an incident yesterday. Added mod_evasive, blocked a few bad bots, Reduced maxclients to 50 (prefork). No events since last night. https://www.bijk.com/p/2199b5ea shows yesterday's outage which will roll off tomorrow. I can grant access to someone who wants a closer look. In my case, I suspect the events are associated with external web server load and are accompanied by dysfunction.This is my only server which gets significant traffic. The others are operating peacefully. LAMP is my bread and butter. This is the proof of the blood. ** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/494476/+attachment/1488104/+files/kern.log -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
I suspect the probability to occur depends on the cpu load. Here on my server is (nearly) no network traffic except two mostly idle ssh sessions. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, »noop« worked for the last two days now. It seems stable. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi! Last night the backup was interrupted again. Our backup process timed out while waiting to be scheduled: [71881.750043] INFO: task mbuffer:8637 blocked for more than 120 seconds. [71881.750531] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [71881.751090] mbuffer1 D 0 8637 4348 0x [71881.751094] 8801ef339c18 0086 00015bc0 00015bc0 [71881.751098] 880405c231a0 8801ef339fd8 00015bc0 880405c22de0 [71881.751101] 00015bc0 8801ef339fd8 00015bc0 880405c231a0 [71881.751104] Call Trace: [71881.751115] [81558e2d] schedule_timeout+0x22d/0x300 [71881.751120] [812b5377] ? kobject_put+0x27/0x60 [71881.751123] [8155a985] ? _spin_lock_irq+0x15/0x20 [71881.751128] [8138b63a] ? scsi_request_fn+0xda/0x5e0 [71881.751131] [815580d6] wait_for_common+0xd6/0x180 [...] This was with »cfq«. This happened at about 80% backup done. I switch back to »noop« and report again. Lars PS: We have no snapshots. There is no lvm device at all on this system. (only SW-RAID6) -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi everybody. The test with cfq was successful too. In our setup and with our purpose the noop was a bit faster. (8:19 hours instead of 8:49 hours) So with a server kernel don't use deadline if you get blocking processes. This seems the solution. Good luck. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
In my case removing all LVM snapshots prevented the errors (and the enormous load). I left the scheduler at deadline. -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, I have success with setting the block-io-scheduler to something different than »deadline« for each block device in our raid arrays. This is with kernel: 2.6.32-24-server I tried »noop« and it worked fine for me. This is not reproduced yet, because a backup lasts more than 12 hours each. Today I'll test cfq and report. To read the current or set the scheduler for each block device through /sys/block/sd*/queue/scheduler. On the other hand you can set it globally with the boot option: »elevator=cfq« (or »noop« or »anticipatory«) Good luck Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Lars, by have success setting you mean avoid the freezes? I'm also running 2.6.32-24-server (but with an adaptec hardware raid) and I haven't had a task blocked for more than 120 seconds. message in my kern.log since Jul 8. However, I think the freezes are still happening just not for 120 seconds, so no log is written. Will keep an eye open and try noop. Cheers -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi Tom, yes I haven't had this »freezes« with noop. With our setup it was reproducable. After some (3-4) hours of heavy io- load from the hdds our process gets blocked for more than 120s and then it stopps itself because it couldn't write to the tape drive any more. With noop the backup (actual two of them in parallel) has run 13 hour without any strange log entry. Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, seems I have the same problem with a mbuffer process reading from a Soft-RAID6 from 24 SATA drives with XFS on it. It's our backup system that writes everything (5.9TB) to tapes. In the end the mbuffer stops with this error: mbuffer: warning: error during output to /dev/st0: Input/output error It seems to me the scheduler is the root of the problem. I'd like to test with upstream kernels but there are no server kernels. I'm running ubuntu 10.04 LTS amd64 server. Which kernel should I choose? Lars -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
@Okkulter, I understand given your setup you may not be able to do this however, if it were possible for you to test with the latest development kernel that would be helpful. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
** Tags removed: kernel-candidate -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
** Tags added: kernel-candidate kernel-reviewed -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
As suggested by Brian Rogers in bug #276476 I'm posting an update here. Hope to attract some attention! I'm running a file server that shares home directories and other directories (~4TB, ext4) to 4 linux clients via nfs and about 20 windows and mac clients via samba. Rsync runs several times per day to mirror all files onto a second server. This seems to be the main trigger for the freezes to happen but I've seen it being caused by other I/O intensive operations, too. Mostly, the file server recovers 'quickly' and the freezes only last for 10 to 60 seconds. Such interruptions occur at least once per hour. When working on a linux client, everything stops (possibly due to the shared ~) until the file server has recovered. On windows clients the program accessing the share freezes. During that time, the load of the server increases rapidly as more and more processes are queuing up for a read/write. Rebooting the server helps but the first 120 second block normally happens within several hours and rebooting every time is not an option. Blocked tasks include pdflush, nfsd and kjournald2. OS is Ubuntu karmic 9.10 on 2.6.31-21-server #59-Ubuntu SMP Wed Mar 24 08:26:06 UTC 2010 x86_64 All packages updated -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
After some more investigations (due to a third crash, and my server unvaillibility) I found something new in the log : In the same time as all the crashes, I have in my apache2 access.log a lot of concurrent access from the same IP (I think from a bad configured corporate proxy) This may be the root cause -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
I have (quiet) the same issue twice in 2 days (on karmic) But I am not using ext4 (only ext3 and jfs) and the first crash I had, it was trackerd the first blocking task : (from kern.log) Apr 19 11:28:43 localhost kernel: [156600.910099] INFO: task trackerd:3486 blocked for more than 120 seconds. (full kern.log on demand) The second time it was cron (but I didn't check if the ran script was IO consuming or not) (from kern.log) Apr 20 14:20:59 localhost kernel: [68160.710147] INFO: task cron:28148 blocked for more than 120 seconds. (log of Apr 20 seems to be polluted by the systReq I misused) No strange update the last days, but I enabled a new django site the day before the first crash (in debug mode) = maybe memory whore. For my specific case (may be different than the one reported here) I suspect 2 causes : * hardware failure. * or bad behavior of something in case of (low memory + huge IO activity.) -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
I think It could be related to this ext4 bug on kernel.org..hopefully an ext4 dev can shed more light on the issue? https://bugzilla.kernel.org/show_bug.cgi?id=14830 ** Bug watch added: Linux Kernel Bug Tracker #14830 http://bugzilla.kernel.org/show_bug.cgi?id=14830 -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Hi, Is this still alive? Should I post here instead: https://bugs.launchpad.net/bugs/276476 ? I've been getting the same errors (INFO: task xyz blocked for more than 120 seconds) since I upgraded to ext4 on my 4TB /home partition. It gets a lot of I/O including rsync backups, smbd and nfs fileserver for ~20 people. I have attached a dmesg. Unfortunately, apport-collect doesn't work for me because the machine doesn't have X and the launchpad logon page doesn't have a selectable [Continue] button in w3m; only cancel works. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 9.10 Release:9.10 Codename: karmic # uname -a Linux io 2.6.31-20-server #58-Ubuntu SMP Fri Mar 12 05:40:05 UTC 2010 x86_64 GNU/Linux ** Attachment added: dmesg http://launchpadlibrarian.net/43530524/dmesg -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
hi there, As a result of this error (behavior?) i switched back from ext4 to ext3 on my 14 TB softraid volume and no more blocking messages. == error with ext4 - definitly greetings to all who waits for a correction I still will have a look on this thx -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
Bug 276476 states that we should file separate bugs for the blocked processes (if I interpret the comments correctly). Can we instead dump everything here? The easiest way to reproduce this is just running rsync or (s)cp with a big file. I see mainly blocked kvm, pdflush and kjournald in kern.log before the server goes down and I have to find a reset button. (doesn't always go down, but I disabled the rsync backup for now.) -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Surbhi Palande (csurbhi) -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
@ Okkulter, can you run appport-collect to attach logfiles with this bug. A complete output of dmesg when you hit the bug would be helpful. Can you also try the latest kernel at: https://launchpad.net/~stefan- bader-canonical/+archive/karmic/+packages to see if it helps ? -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Triaged -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494476] Re: Smbd, kjournald2 and rsync blocked for more than 120 seconds while using ext4.
** Tags added: karmic -- Smbd,kjournald2 and rsync blocked for more than 120 seconds while using ext4. https://bugs.launchpad.net/bugs/494476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
