cobbler hardlink error

[Bryan Schneiders]

cobbler-2.0.1-1.fc10.noarch
hardlink-1.0-7.fc9.i386
cobbler-web-2.0.1-1.fc10.noarch

I've had a cronjob to run cobbler hardlink on a regular basis since 1.6.x.  Before 2.0 it ran without errors.  Now with 2.0 and 2.0.1 I get this:

task started: 2009-10-07_230004_hardlink
task started (id=Hardlink, time=Wed Oct  7 23:00:04 2009)
now hardlinking to save space, this may take some time.
running: /usr/sbin/hardlink -c -v /var/www/cobbler/ks_mirror /var/www/cobbler/repo_mirror

Directories 201
Objects 138728
IFREG 138501
Mmaps 19857
Comparisons 130504
Linked 2437
saved 33697792
returned: 0
Exception occured: <type 'exceptions.NameError'>
Exception value: global name 'rc' is not defined
Exception Info:
  File "/usr/lib/python2.5/site-packages/cobbler/remote.py", line 94, in run
    rc = self._run(self)
   File "/usr/lib/python2.5/site-packages/cobbler/remote.py", line 188, in runner
    return self.remote.api.hardlink(logger=self.logger)
   File "/usr/lib/python2.5/site-packages/cobbler/api.py", line 759, in hardlink
    return linker.run()
   File "/usr/lib/python2.5/site-packages/cobbler/action_hardlink.py", line 59, in run
    return rc

!!! TASK FAILED !!!

[sligtly OT]: how to make use of hardlink, WAS: Re: cobbler hardlink error

[Christian Horn]

Hi

the hardlink-package also exists in rhel5u4 base repo.

Just played a bit bit it, wondering how other people use it?
The way i would find stuff useful is

a) i start hardlink for inspecting all my repo-directories
b) it creates hardlinks for duplicate files
c) as soon as i update one of the files i get a copy-on-write,
so the two files are no longer pointing to the same inode.
Parts a) and b) are how it currently works, not part c).
As soon as i modify the file at the inode both filenames point 
to the same modified file.  I know this is 'how it works' currently,
but for my cobbler-directory i cannot keep track of all hardlinked
files and dissolve this for myself bevore changing one of the
underlying files.

Do i miss something?
How do you people use hardlinks/cobbler, after fedding directories
to hardlink never touching those files for modification again?

Christian

[sligtly OT]: how to make use of hardlink, WAS: Re: cobbler hardlink error

[Jasper Capel]

----- "Christian Horn"  wrote:
> Hi
>
> the hardlink-package also exists in rhel5u4 base repo.
>
> Just played a bit bit it, wondering how other people use it?
> The way i would find stuff useful is
>
> a) i start hardlink for inspecting all my repo-directories
> b) it creates hardlinks for duplicate files
> c) as soon as i update one of the files i get a copy-on-write,
> so the two files are no longer pointing to the same inode.
> Parts a) and b) are how it currently works, not part c).
> As soon as i modify the file at the inode both filenames point 
> to the same modified file.  I know this is 'how it works' currently,
> but for my cobbler-directory i cannot keep track of all hardlinked
> files and dissolve this for myself bevore changing one of the
> underlying files.
>
> Do i miss something?
> How do you people use hardlinks/cobbler, after fedding directories
> to hardlink never touching those files for modification again?

I use hardlink to de-duplicate RPMs. RPMs that get matched together are of a specific version, and I think these RPMs shouldn't ever change, a new version of this RPM should simply appear.

Cheers,
Jasper