![]() ![]() When running my monthly backups things start queuing up till nothing works. Under heavy IO it can freeze for a bit, then may or may not return. Let me know what other info I can provide. So I performed the copy operation in VTE. The session 6 was started because the pulseaudio constantly crashed and resulted in high Gnome Shell CPU usage. ![]() Nov 1 20:24:42 localhost kernel: Initializing cgroup subsys cpu Nov 1 20:24:42 localhost kernel: Initializing cgroup subsys cpuset Nov 1 20:24:42 localhost kernel: imklog 5.8.5, log source = /proc/kmsg started. Nov 1 20:21:42 localhost systemd-tmpfiles: Successfully loaded SELinux database in 52ms 820us, size on heap is 363K. Nov 1 20:18:50 localhost dbus-daemon: ** Message: No devices in use, exit Nov 1 20:18:37 localhost gnome-session: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface= method=IsInhibited Nov 1 20:18:33 localhost systemd-logind: New session 6 of user lvp. The freeze happened in less than two minutes: I was copying a 7.5G file to NTFS formatted USB thumb disk. Here are the lines in /var/log/messages before freeze(20:18:50) and after I forced power off and restarted(20:21:42). > Try running the kernel-debug kernel to see if that makes any additional output > There's not much to go on here without any backtraces. So I guess the cause lies somewhere else. I was still caught two freezes when copying between internal and USB-connected external hard drive. > or boot with kernel option elevator=deadlineįor me, or at least 3.1.0.1.fc16.i686, the switching to deadline scheduler only reduce the chances of freeze. > echo "deadline" > /sys/block/sdX/queue/scheduler > scheduler to the deadline scheduler, and the problem immediately cleared. I ssh'd in from another machine and noticed high iowait, but > (gigabytes) to a USB attached flash card. > I was able to easily recreate the problem, by copying a large amount of data Grsync windows 10 locks up plus#Platform: Core i7 920 (2.67GHz Bloomfield, not O/C'd), x86_64 kernel versions as above, Asus P6TSE with 12GB DDR3 DRAM, md RAID5 (4x Samsung HD103SJ all clean with no errors according to smartctl) plus 2TB Werstern Digital drive acting as temporary backup while I reconfigure the RAID partition & a 320Gb Hitachi for system files. Reboots & freezes after a few 10s of seconds. ![]() Version-Release number of selected component (if applicable): I'm not sure that this is RAID specific though - the machine also crashed during a "yum install" of some stuff which would have gone to the system partition on a separate Hitachi Deskstar T7K500 - this drive is a bit older but, again, shows no problems with smartctl. All the drives are fairly new (18 months) The filesystem in question is an md RAID5 of 4 Samsung drives with an ext4 filesystem. I've tried both 2.6.38.6-26 which was the original F15 kernel and 2.6.38.8-35 which is the current one. I have successfully copied the data in F14 (kernel 2.6.36-1), and am about 90 minutes into verifying the copy (with that much data chances of an error somewhere become rather more likely - it'll take a few hours more to compare the whole tree) but both the original copy and an attempt to verify the copy crashes in F15 very quickly. Unfortunately no OOPS or any other diagnostic to attach, either the X window session froze with a blank screen requiring a reboot or more often the machine simply rebooted. Set out to back-up approx 1.3TB of data (mostly camcorder footage) to a new hard 2TB drive but experienced freezes or reboots after a few tens of seconds with anything that caused heavy disk I/O such as resize2fs or rsync. Grsync windows 10 locks up install#Clean install to separate partition on spare HD with no problems. Heavy disk I/O crashes or freezes Fedora 15, possibly MD RAID specific. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |