my HDA is crashing on exploding messages file

[wvdlee]

Hi,

after apprximately two days of operation my hda starts to fill up the messages file with

Code: Select all

Jul 3 21:11:19 localhost smbd[22670]: [2012/07/03 21:11:19, 0] smbd/notify_inotify.c:253(inotify_handler) Jul 3 21:11:19 localhost smbd[22670]: No data on inotify fd?!

until my root partition is full and the HDA crashes.
in this forum topic http://forums.amahi.org/viewtopic.php?f ... 3&start=10

G Boudreau suggested a shortage of inodes, whatever that may be, but df -i does not report a shortage, or does it?

Code: Select all

Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/VolGroup-lv_root 3203072 179457 3023615 6% / tmpfs 224639 6 224633 1% /dev/shm /dev/sda1 51200 44 51156 1% /boot /dev/mapper/1Tb_schijf-tb_data 61054976 58084 60996892 1% /var/hda/files /dev/mapper/VolGroup-lv_downloads 42352640 16 42352624 1% /var/hda/files/downloads /dev/sdc1 61054976 140274 60914702 1% /media/seagateusb localhost:/media/seagateusb/.private/.snapshots/ 61054976 140274 60914702 1% /var/hda/files/backup

I am using an old amahi on fedora 12:
Systeem: 2.6.32.26-175.fc12.x86_64 , x86_64
Platform: 5.6.11-1
Core: 3.6-1
Bedrijfstijd: 21:34:58 up 2 days, 10:14, 2 users, load average: 4.00, 3.61, 3.42

Upgrading would probably solve the problems, but it takes a lot of work to upgrade to amahi on fedora 14 which is almost EOL. So I would like to wait for a stable release under fedora 17 before I upgrade.

Does anybody Know what's going on on my server? what's causing my messages file to

[bigfoot65]

Not sure what could be the cause. Wonder if you could turn off the messaging? Also be aware there will not be an upgrade path to Fedora 17. It will require a new install due to the vast changes with both it and Amahi.

No estimate on when Fedora 17 will be ready as we are just beginning to work it now that Ubuntu is pretty much stable.

[wvdlee]

Fedora or Ubuntu I dont really mind. I only need a stable release of amahi with crashplan, ajaxplorer and a torrent app.
And I would really like a way to upgrade without having to pump all my data around.
Why not make a standard setup for amahi where the data is always on a different partition that is recognized during an upgrade install? that would make life much easier.
I suppose I could do something like that myself, but I am not really into linux to do that easily, thats why I am using Amahi.

[bigfoot65]

Understand. We are always looking for ways to improve Amahi. That might be possible down the road, but with all the install scenarios and hardware configurations, it's hard to cover them all.

Then there is the issue with potential data loss with an automated process. Just not a easy to attain feature for a project that is open source and backed by a small team of volunteers.