compressed file xxx is corrupt and unrecoverable

Recently our Netware 6 sp4 server started having a volume issue that is compressed.  I am wondering what are the best steps in trouble shooting this issue and possibly fixing it.  We would like to retreive the data as it is more recent than the current backup. The other volumes are fine.  There is also a message that comes up on the server that says 'FreeObject detected object is already free'   I have not found much on this message either.
lthorupIT ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
This can happen when the free space on the Volume gets too low. Is this an NSS or a Traditional/FAT Volume?

You can generate some free space, probably, by purging the filesystem of deleted files that have not yet been put into the pool of free space. Unless a Volume or subdirectory structure is flagged Purge Immediate, deleted files are retained for a (configurable) timeperiod before the space they occupy is actually made available to other files. On a highly dynamic Volume - with lots of files being constantly created and deleted - the Volume can be starved for space even tho the undeleted files on the Volume do not consume all the space.

Unfortunately, the file that the system reported as "corrupt and unrecoverable" is probably just that. It went to decompress it, it lacked sufficient space, and the result was a mess. I hope you have a backup that was made with a NetWare-aware backup software, properly configured for your environment. NetWare is no different than any other platform - if you don't use the right tools for the platform, or you don't use the tools correctly, you'll have problems. Same rule applies to Linux, *NIX, Windoze, OS/400, S/36, OS/2, VMS, etc. etc. etc.

If your Volume is just low on disk space, consider adding more storage. NetWare's disk compression options date back to the mid-90s, when disk space was still relatively expensive (>$10/MB). Its cheap now. I don't use Disk Compression on my NetWare servers - disk space is cheap, why bother?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lthorupIT ConsultantAuthor Commented:
Thanks for the response.
It is probably true then that automatic compression does not happen until the volume gts to a certain capacity?  I agree with you that disk space is cheap at this point and there is no need to allow compression.   I don't suppose that using any utilities like vrepair will help salvage any of these files.  Someone told me that possibly using vrepair and removing name spacing then readding name spacing may fix the corruption.  What are your thoughts?
ShineOnCommented:
That depends, as PsiCop alluded to, on whether you're using NSS or traditional (FAT) volumes.  VREPAIR is for FAT volumes.  There's a whole other set of utilities for NSS volumes.
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

PsiCopCommented:
Yep - it *might* work, depending on whether your Volume is using the Traditional/FAT or NSS filesystem, and what namespaces and so forth. As ShineOn mentioned, VREPAIR is a tool specific to the Traditional/FAT filesystem, and the tools in NSS are different.
PsiCopCommented:
As for what triggers automatic compression, its based on how many days since the file was last accessed, and has nothing to do with capacity. I believe the defaults will compress any file which has not been accessed for at least 14 days.
ShineOnCommented:
... and there's a minimum compression gain factor too.
pgm554Commented:
>Someone told me that possibly using vrepair and removing name spacing then readding name spacing may fix the corruption.  What are your thoughts?
DO NOT DO IT ! All of your long name files will become truncated and you will not get them back by adding long names again.

If you need to recover damaged files Ontrack has a utilityfor NW.

http://www.ontrack.com/odrn/
ShineOnCommented:
odrn - is that short for oh, darn? hehe...
PsiCopCommented:
*chuckle*

Yeah, I wondered about that namespace advice, but I've never been in this situation...

Yeah, there is a minimum requirement for the amount of storage recovered by compression - prevents the OS from compressing already-compressed files, like .ZIPs.
elf_binCommented:
You need to restore the data using a 3rd party utility like Server Magic, OnTrack or (possibly) Portlock.  I doubt VREPAIR or NSS /Verifywill work since it scans the metadata on the disk and attempts to fix the filesystem - not the data.
You can control compression settings using the SET commands (like SET ENBALE COMPRESSION = OFF)

Best of luck.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.