Hi, This is not a z/Linux or z/VM question but Let me ask you guys something about ext3... I guess that most of you are using it in production... How is it possible that i am using ext3 in my production systems and face stuff like: 1. Corrupted FS during normal work that needs to be fixed with fsck or worse restore from a backup 2. Resizing a FS requires me to fsck before I resize (as if the FS does not trust itself to be valid forcing me to umount the FS before a resize) 3. Resizing a FS offline actually corrupts the FS 4. The fstab parameters, that states that it is normal to fsck your FS every boot or every several mounts... 5. FS is busy although it is not mounted or in use by anyone... 6. fuser command will not always show the using processes 7. open files can be removed without any warning from the rm command. 8. removing files from the FS will not free up space in the FS
I can go on with Linux stuff that bother me but lets stick to ext3, and i guess maybe some of my issues might not be accurate. I am a z/OS system programmer and maybe i am expecting for too much, but even windows don't have this kind of stuff anymore... I am using redhat V5.2 (not too old) and recently was asked from my local redhat representative to upgrade my kernel to V5.6 (2.6.18-238). To my huge surprise i am still seeing this kind of issues even with the new kernel... Am i alone here? how can this be? Why are we all using linux if it is still not ready for production? will ext4 fix that or is it just bigger, faster but based on the same unstable technology? Blowing out some steam... Offer Baruch ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
