CODEWITHSUNDEEP
filesystemsposixhardlink
Ben Clifford
Ben Clifford

Reputation: 1418

Replacing a file with a hardlink to another file atomically

I have two directory entries, a and b. Before, a and b point to different inodes. Afterwards, I want b to point to the same inode as a does. I want this to be safe - by which I mean if it fails somewhere, b either points to its original inode or the a inode. I especially don't want to end up with b disappearing.

mv is atomic when overwriting, and ln appears to not work when the destination already exists. So it looks like i can say:

ln a tmp
mv tmp b

which in case of failure will leave a 'tmp' file around, which is undesirable but not a disaster.

Is there a better way to do this?

(What I'm actually trying to do is replace files that have identical content with a single inode containing that content, shared between all directory entries.)

Upvotes: 4

Views: 1309

Answers (2)

mtd
mtd

Reputation: 2364

ln a tmp && mv tmp b || rm tmp

seems better, as then if ln fails, the mv will not get executed (and clutter up stderr when it fails).

Upvotes: 3

Joshua
Joshua

Reputation: 43270

 ln a tmp ; mv tmp b

is in fact the fastest way to do it atomically, as you stated in your question.

(Nitpickers corner: faster to place both system calls in one program)

Upvotes: 1

Related Questions