0

In rhel 7.8 I have a folder called /study that has a bunch of data. It was ~500GB in size.

I did gzip -9r /study and it reduced that folder to 294GB as reported by du -sh /study

I then did tar -cf study.tar /study and now have a single file named study.tar at 294GB.

I will first copy it to a locally mounted NTFS disk (using ntfs-3g under RHEL 7.8) and then will move that single 294GB tar file to some company provided CIFS share.

Other than time to copy and finding available disk space are there any foreseeable problems I should be aware of, before I do a rm -r /study on the original to free up disk?

7
  • I'd copy it back from the network share and run md5sum on it as well as the original and ensure the data made it round trip before deleting the source. – Aaron D. Marasco Oct 20 '20 at 21:49
  • Why convert the individual files to a tarball? Why not just copy the (compressed) files? One less step to worry about and it reduces interdependencies – roaima Oct 20 '20 at 22:00
  • @roaima maybe to preserve file permissions? I don't know what ntfs is capable of. On that point how big files can ntfs handle? I remember "once upon a time" when I think fat could not hold very big files. – Lucas Oct 20 '20 at 23:25
  • If you want to retain permissions consider using tar or some other archiver on each file separately – roaima Oct 21 '20 at 6:46
  • Am I correct in assuming you have one tarball containing thousands of *.gz files? – Jaap Joris Vens Oct 21 '20 at 18:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.