I'm guessing the issue is with /data. Does this problem occur when trying to move or copy a very large file to this partition. How big is that partition anyhoo.

permata

Newbie

Posts: 6

Loc: Kuala Lumpur

3+ Months Ago

Well it used to happen with /data but I manage to reduce the size by backing up few files. It will happen again everytime it reaches 52% utalization. Same goes to /data1.

BTW the data that being saved is a small text record which everytime a user access it will start saving a log.

It seams to me that Linux doesnt seams to allow me to write on any partation once it reaches above 50%

BTW the size for /data is 6.6GB & /data1 is 4.4GB.

Please advise

Rico16135

Novice

Posts: 26

Loc: Arlington, Texas

3+ Months Ago

The only possible reason I can come up with is user quotas. I can't recall the program name, but there is a program that limits a users available disk usage. Perhaps that is a clue to your problem. I'll try and research it a bit more.

Rico16135

Novice

Posts: 26

Loc: Arlington, Texas

3+ Months Ago

could you please post your contents of /etc/fstab? If it is a disk quota problem, then there will be an entry in your fstab.

quotacheck: Can't find filesystem to check or filesystem not mounted with quota option.

Please advise

TQ

Daemonguy

Moderator

Posts: 2700

Loc: Somewhere outside the box in Sarasota, FL.

3+ Months Ago

Hmm. Odd that. Might be that ext3 is still using file space of deleted files until they are deallocated.

permata

Newbie

Posts: 6

Loc: Kuala Lumpur

3+ Months Ago

mmm is there a way to solve this... or any tools that can help me repair this.....

TQ

Daemonguy

Moderator

Posts: 2700

Loc: Somewhere outside the box in Sarasota, FL.

3+ Months Ago

Well, if it's ext3 issue, that was a bug IIRC. You may want to do some due diligence and hunt down that information.
The ext3 mailing list could help; https://listman.redhat.com/mailman/listinfo/ext3-users/

Some blocks are allocated for the super user too, though it should not be that much, (with ext3). I tcould just be a jfs issue; do you really need a journaling file system? If not, try reverting back to ext2.