Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I had 20 gb sitting unclaimed on my drive and had to move some Vmware machines. I used fdisk to make it a partition, rebooted and mounted it. However when copying files to it, it gives me an error about not being able to maintain ownership, then when trying to load the machines in vmware, it gives me a variety of errors claiming it can't create logs, then says it can't lock the file, then fails to start the virtual machine. Anyone know how I can clear this up? I assume its the fact that the partition was mounted as root, but everytime I try to chgrp or chown the directory the partition is mounted to (even when unmounted) it fails.
I've added it to my fstab. Would rebooting and letting the system mount it help?
What filesystem does it use? I have encountered many of those errors when trying to copy data to a FAT-drive (fat16/32); it doesn't support ownerships so it makes sense. If you created the filesystem as fat, I suggest that if you don't use Windows on it, switch it to something else, like ext2 or ext3 (latter one is journalled).
The following two commands (use either one) make an ext3 file system. mke2fs -j /dev/hdb1 mkfs.ext3 /dev/hdb1
The only reason I ask is that you stated you creeated a partition and mounted it but never mentioned formatting it. I wasn't sure if we were supposed to assume you formatted it as EXT3 or if you might have fogotten to do that step..
I almost didn't post that solution thinking nah he wouldn't forget thaty step would he ? But then again the first rule of troubleshooting is to look at all the obvious stuff first.. (is it plugged in ? Is it turned on ? ) Then move on to the more difficult steps. heh amazing the things we forget when we are in a rush ehh ? Glad you got it all worked out