HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- link failed
Operating System - HP-UX
1833730
Members
2426
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2008 11:51 AM
02-14-2008 11:51 AM
link failed
what causes this error when doing a simple copy
link failed: aoqdesg.plx: File exists
this was the command
cp *.plx /u01/app/sghe/inb/LCCC/fmx/base/
the copy worked all the .plx's were copied ??
link failed: aoqdesg.plx: File exists
this was the command
cp *.plx /u01/app/sghe/inb/LCCC/fmx/base/
the copy worked all the .plx's were copied ??
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2008 06:28 PM
02-14-2008 06:28 PM
Re: link failed
Hi
Seems "aoqdesg.plx" already exist on the target directory.
Or Any soft link / hard link for the file aoqdesg.plx is already there in target directory.
Thanks & Regards
Ramesh
Seems "aoqdesg.plx" already exist on the target directory.
Or Any soft link / hard link for the file aoqdesg.plx is already there in target directory.
Thanks & Regards
Ramesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2008 06:52 PM
02-14-2008 06:52 PM
Re: link failed
The "cp" command would normally copy over an existing file or link with the same name.
SOmething is wrong with the "aoqdesg.plx" file in the destination folder. The "link failed" message means that the name aoqdesg.plx can not be created in the destination folder as a directory entry and not as file contents.
Can you post the output
ll -i /u01/app/sghe/inb/LCCC/fmx/base/aoqdesg.plx
Are there any errors (inode related) in the syslog?
You can do a compare of the source and target directories visually and using diff and dircmp.
SOmething is wrong with the "aoqdesg.plx" file in the destination folder. The "link failed" message means that the name aoqdesg.plx can not be created in the destination folder as a directory entry and not as file contents.
Can you post the output
ll -i /u01/app/sghe/inb/LCCC/fmx/base/aoqdesg.plx
Are there any errors (inode related) in the syslog?
You can do a compare of the source and target directories visually and using diff and dircmp.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2008 11:09 PM
02-14-2008 11:09 PM
Re: link failed
"cp" is generally not a good way to duplicate
the contents of a directory. The results can
depend too much on the form of the files
being copied (and whose "cp" you're using).
For example:
td191> ls -l
total 16
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.hln
lrwxrwxrwx 1 antinode 513 8 Feb 15 02:02 file.sln -> file.txt
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.txt
td191> cp -p * ../dir2
td191> ls -l ../dir2
total 24
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.hln
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.sln
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.txt
And a second time:
td191> cp -p * ../dir2
link failed: file.sln: File exists
link failed: file.txt: File exists
On the other hand (after emptying dir2):
td191> tar cf - . | ( cd ../dir2 ; tar xf - )
td191> ls -l ../dir2
total 16
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.hln
lrwxrwxrwx 1 antinode 513 8 Feb 15 02:04 file.sln -> file.txt
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.txt
I prefer the latter result.
the contents of a directory. The results can
depend too much on the form of the files
being copied (and whose "cp" you're using).
For example:
td191> ls -l
total 16
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.hln
lrwxrwxrwx 1 antinode 513 8 Feb 15 02:02 file.sln -> file.txt
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.txt
td191> cp -p * ../dir2
td191> ls -l ../dir2
total 24
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.hln
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.sln
-rw-rw-rw- 3 antinode 513 28 Feb 15 01:52 file.txt
And a second time:
td191> cp -p * ../dir2
link failed: file.sln: File exists
link failed: file.txt: File exists
On the other hand (after emptying dir2):
td191> tar cf - . | ( cd ../dir2 ; tar xf - )
td191> ls -l ../dir2
total 16
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.hln
lrwxrwxrwx 1 antinode 513 8 Feb 15 02:04 file.sln -> file.txt
-rw-rw-rw- 2 antinode 513 28 Feb 15 01:52 file.txt
I prefer the latter result.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP