search for: thompsk

A hardware vendor shipped us a product installed with RedHat 8.0 with all file systems created as ext3. This system has about 800 GB of space which we use for buffering email files (in RFC format). Several weeks into the project and with millions of emails stored, we started seeing "out of inode" (something like that) error messages in the /var/log/messages. Are inodes fixed on ext3

Hi, got a very severe problem. I have two hard drives in my RS server and I am getting the secondary drive removed. Here's the problem. After the secondary drive is removed, the server fails to bootup completely, crashing at fsck. The server boots up fine when the secondary drive is put back in however. Has anyone ever encountered this problem before? Could the problem be to references to

I'm using RedHat 7.2 with kernel 2.4.18-26.7.xsmp and root mount using ext3. And I have simple test.pl script: #!/usr/local/bin/perl open FILE, ">testfile"; while(1){ print FILE "Test.\n" or die $!; } It's died when the file size is 2147483647 and give error message: "File size limit exceeded" and I run "cat testfile testfile >>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 subject about says it all. should this only be done once per device or periodically? thanks! - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://www.linux-sxs.org and http://jobs.linux-sxs.org Illiterate? Write for help! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)

Hello all, I know this question is (strictly speaking) off topic, but if someone could at least point me in the right direction, I would be most grateful. I have an older system (RH 6.2, overdue for upgrade) with an ext2 partition that was pushing 99% filled. I did some space recovery and I have it down to around 90% utilization now. I have rebooted the unit, and brought it up single-user

Greetings. Total newbie with Ext3. I selected when I upgraded my system to RH7.2. I upgraded my system again to RH8.0. Here is some info: [root@world root]# cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 none /dev/shm tmpfs rw 0 0 none /dev/pts devpts rw 0 0 /dev/hdd1 /mnt/genericdata1 ext2 rw 0 0 Ok, so

Dear all, Due to the power failure, so i need to restart my redhat linux server. but i got below error messages, pls everybody can help/teach me fix the problem by return mail. ------------------------------------------------------------------------------------------------------------------------------------------------ Yours system appears to have shut down uncleanly Press Y within 1 seconds

Does anyone know of any Linux-based filesystem that does file-level auditing and logs based on username? Does ext2/3 do such auditing (stock or with patches)? I would like a filesystem that can be told to audit and log file deletions and log the username that deleted the file (similar to auditing on NTFS). I know, I should be using file permissions to prevent this type of deletion from

Folks: Is there a limit to the number of arguments that can be passed to fileutils programs such as mv or rm ? If yes, is it filesystem dependant/kernel config dependant/fileutils version dependant? Can this maximum limit be tuned/controlled ? I googled on it a bit, but couldn't find anything much more relevant than a message in the OS-X forum.