[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Reducing HDD writing affect on whole system.



Thank You for Your time and answer, Martin:

>Ok, before doing anything else try to repair your Ext4 filesystem:
>
>[  154.732424] composite sync not supported
>[  299.358408] composite sync not supported
>[  304.096062] EXT4-fs (sda2): error count: 15
>[  304.096073] EXT4-fs (sda2): initial error at 1313766195: 
>ext4_mb_generate_buddy:736
>[  304.096083] EXT4-fs (sda2): last error at 1315801717: 
>ext4_reserve_inode_write:5619
>[  387.290671] composite sync not supported
>
>These errors may have an relation to slow performance. Are there any
>other Ext4 related errors?

I have repaired the FS - when done it did not tell that any
modifications had a place, so after the check boot process went as
usual (did not reboot, nor any messages did show).

I have tried again - copying, and see same waiting for the ?kernel.
Though dmesg shows me now the following:

$ dmesg |grep error

[    0.908073] ssb: Failed to register PCI version of SSB with error -12

[    0.908166] b43-pci-bridge: probe of 0000:05:00.0 failed with error
-12

[   11.010837] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

[   19.630649] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: errors=remount-ro

[   82.183242] EXT4-fs (sda2): re-mounted. Opts:
errors=remount-ro,commit=0

[   84.304981] EXT4-fs (dm-0): re-mounted. Opts:
errors=remount-ro,commit=0

Seems weird - why it is being REmounted instead of just being
mounted?

>You might want to copy everything what goes to another disk or create
>a disk dump and trial run the fsck from there. Are there any

I have no such ability for now...

>input/output errors in kern.log / syslog?

No. The same as in dmesg.

>Is sda2 the partition you are doing the copy on?


Reply to: