Ошибка Disk quota exceeded (122) при наличии свободного места

Вчера не сервере midnight commander (mc) ругался при запуске:

Cannot create temporary directory /tmp/mc-prsl: Disk quota exceeded (122)

Temporary files will be created in /tmp

Press any key to continue...

а затем начали валится мускульные базы по аналогичной ошибке:

Dec 19 16:02:09 sd-16440 mysqld[13255]: 081219 16:02:09 [ERROR] /usr/sbin/mysqld: Disk is full writing '/var/lib/mysql/doblo2clubru/ibf_p osts.MYI' (Errcode: 122). Waiting for someone to free space... Retry in 60 secs

При том, что места достаточно:

/dev/md1 20313224 3827556 15461932 20% /

и квот никаких не стоит.

Пока перенесли базы в /home куда подключен:

/dev/md2 463592296 133915200 306313372 31% /home

Но проблема может повториться. Предварительно: некие лимиты файловой системы на количество фалов.

Вопрос: как точно выяснить с чем связана проблема, и как ее можно решить/оптимизировать?

Исходные данные:

Debian-etch-amd (core2duo)

fs: ext3 (два sata диска 500гигов в зеркале)

sprokofiev добавил 20.12.2008 в 10:20

Вот, что обнаружил в последнем dmesg:

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

md: Autodetecting RAID arrays.

md: Scanned 6 and added 6 devices.

md: autorun ...

md: considering sdb4 ...

md: adding sdb4 ...

md: sdb3 has different UUID to sdb4

md: sdb1 has different UUID to sdb4

md: adding sda4 ...

md: sda3 has different UUID to sdb4

md: sda1 has different UUID to sdb4

md: created md2

md: bind<sda4>

md: bind<sdb4>

md: running: <sdb4><sda4>

raid1: raid set md2 active with 2 out of 2 mirrors

md: considering sdb3 ...

md: adding sdb3 ...

md: sdb1 has different UUID to sdb3

md: adding sda3 ...

md: sda1 has different UUID to sdb3

md: created md1

md: bind<sda3>

md: bind<sdb3>

md: running: <sdb3><sda3>

raid1: raid set md1 active with 2 out of 2 mirrors

md: considering sdb1 ...

md: adding sdb1 ...

md: adding sda1 ...

md: created md0

md: bind<sda1>

md: bind<sdb1>

md: running: <sdb1><sda1>

raid1: raid set md0 active with 2 out of 2 mirrors

md: ... autorun DONE.

md: Loading md1: /dev/sda3

md: couldn't update array info. -22

md: could not bd_claim sda3.

md: md_import_device returned -16

md: could not bd_claim sdb3.

md: md_import_device returned -16

md: starting md1 failed

EXT3-fs: INFO: recovery required on readonly filesystem.

EXT3-fs: write access will be enabled during recovery.

kjournald starting. Commit interval 5 seconds

EXT3-fs: md1: orphan cleanup on readonly fs

ext3_orphan_cleanup: deleting unreferenced inode 645064

ext3_orphan_cleanup: deleting unreferenced inode 645062

ext3_orphan_cleanup: deleting unreferenced inode 734408

ext3_orphan_cleanup: deleting unreferenced inode 734407

ext3_orphan_cleanup: deleting unreferenced inode 734406

ext3_orphan_cleanup: deleting unreferenced inode 734405

ext3_orphan_cleanup: deleting unreferenced inode 734404

ext3_orphan_cleanup: deleting unreferenced inode 636639

EXT3-fs: md1: 8 orphan inodes deleted

EXT3-fs: recovery complete.

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem) readonly.

Freeing unused kernel memory: 304k freed

Adding 522104k swap on /dev/sda2. Priority:-1 extents:1 across:522104k

Adding 522104k swap on /dev/sdb2. Priority:-2 extents:1 across:522104k

EXT3 FS on md1, internal journal

w83627hf: Found W83627THF chip at 0xa00

w83627hf w83627hf.2560: GPIO5 disabled, no VID function

kjournald starting. Commit interval 5 seconds

EXT3 FS on md0, internal journal

EXT3-fs: mounted filesystem with ordered data mode.

kjournald starting. Commit interval 5 seconds

EXT3 FS on md2, internal journal

EXT3-fs: mounted filesystem with ordered data mode.

Возможно как-то связано, пожалуйста выскажите свои предположения.