- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: drive "device busy" in one machine, but ok in ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО10-28-2007 03:18 PM
тАО10-28-2007 03:18 PM
drive "device busy" in one machine, but ok in other
i've got a weird problem.there is a drive in 10/180 library,which is in a SAN enviroment. after i load a tape into the drive, i try to offline the tape in one machine so i can unload the tape, it said "device busy". but i repeat the same procedure in other machine, which is in the same SAN with the machine i mentioned before, and it is ok, not error messages. so what can this be? i think i could conclude that the library was ok, right?
thank you for your reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2007 08:37 PM
тАО10-28-2007 08:37 PM
Re: drive "device busy" in one machine, but ok in other
Do You have the same library driver on both servers?
Thanks,
Jesus Fdez
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2007 02:54 PM
тАО10-29-2007 02:54 PM
Re: drive "device busy" in one machine, but ok in other
the library is in the SAN enviroment, all the servers are connecting into the same SAN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2007 03:04 PM
тАО10-29-2007 03:04 PM
Re: drive "device busy" in one machine, but ok in other
You can test for that case but it isn't easy. Probably the best would be to power down the library (or just the drive) and the server that can send commands to the drive then power up just the library (or drive). The second server should be able to use the drive if the first server hasn't reserved it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2007 03:38 PM
тАО10-29-2007 03:38 PM
Re: drive "device busy" in one machine, but ok in other
the truth is all other servers could handle drive 0 in the library, except one server. here handle only means that mt command could apply to that drive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2007 08:48 PM
тАО10-30-2007 08:48 PM
Re: drive "device busy" in one machine, but ok in other
Curtis gave you the most common answer to this situation, in your case, you may also have another situation (may be)
if you have a windows server, some time, if you do not have persistent binding, it may be that the drive enumaration change, so if you try to access drive 0, your command can go to drive 5 for example, and then, if the specific drive is doing something, you will get the "device busy"
You can have several situations causing this behavior, further investigations may be needed.