.tar.gz 111GB extracting fails

rajthampi · 05-22-2015, 05:23 AM

Quote:

Originally Posted by pan64

probably there are different users (user ids) configured and the user/group who created the tar does not exist on the target host therefore it has no right to create files/dirs.
Tar handles only ids, so you may have the the same username with different ids to make such conflicts.

Hello pan64

As you could see, I posted this question to beginners area, as my exposure towards Linux is very limited. I interact with it regularly, as a developer for Oracle applications, however I don't know much about how the users, their ids are involved in certain few things.
Coming from a purely Windows environment, I understand that, the root has the highest level of privileges and tar is only extracting the files! Does tar care for which user created the tar file and who is extracting them?

How about creating the same oraprod in the target system and changing the owner of the tar.gz to oraprod?

regards,

pan64 · 05-22-2015, 05:47 AM

first just check (if it was really true). You can use the command: id <username> and you will see the user ids (numbers) - on both hosts.
Next you can try to extract using tar with options --no-same-owner --no-same-permissions
But would be nice to tell us the result of that check and also explain which user was used and which commands were executed (exactly) to create and extract that tar file.

rajthampi · 05-22-2015, 06:29 AM

Quote:

Originally Posted by pan64

first just check (if it was really true). You can use the command: id <username> and you will see the user ids (numbers) - on both hosts.
Next you can try to extract using tar with options --no-same-owner --no-same-permissions
But would be nice to tell us the result of that check and also explain which user was used and which commands were executed (exactly) to create and extract that tar file.

Hello pan64

I created the user with same name and changed the ownership of the archive and started the extracting once again. It looks like the entire errors thrown were due to some other read+write permissions.
Once I get an output I will update it to you.

regards and thank you very much for the patience

rknichols · 05-22-2015, 09:53 AM

Quote:

Originally Posted by rajthampi

Code:

tar: u05/oraprod/PROD/db: Cannot utime: Read-only file system
tar: u05/oraprod/PROD/db: Cannot change mode to rwxr-xr-x: Read-only file system
tar: u05/oraprod/PROD/db: Cannot change ownership to uid 500, gid 300: Read-only file system
tar: u05/oraprod/PROD: Cannot utime: Read-only file system
tar: u05/oraprod/PROD: Cannot change mode to rwxr-xr-x: Read-only file system
tar: u05/oraprod/PROD: Cannot change ownership to uid 500, gid 300: Read-only file system
tar: u05/oraprod/scripts: Cannot mkdir: Read-only file system

You will have to find out why the filesystem has become read-only. Perhaps there is something in /var/log/messages that indicates what error caused that.

rajthampi · 05-24-2015, 02:30 AM

Quote:

Originally Posted by rknichols

You will have to find out why the filesystem has become read-only. Perhaps there is something in /var/log/messages that indicates what error caused that.

Hello rknicholas

I don't have a clue, the disk was remounted and I was able to extract the files. What I observed until almost 48 hours of efforts are

if I move the tar.gz files using "cp", the md5sum are different
if I move the same files using "scp", the md5sum are same and I can extract the files without any problems using tar

It looks kinda strange, however, finally I was able to extract the files to a second server, even though the process took around 834 minutes to extract a 111gb tar file.

thanks to everyone who contributed to the question.

regards,