- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: touch on /dev/vg00/lvol9
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
тАО08-13-2006 09:39 PM
тАО08-13-2006 09:39 PM
touch on /dev/vg00/lvol9
touch /dev/vg00/lvol9
Now instead of:
brw-r----- 1 root sys 64 0x000009 Jun 17 08:36 /dev/vg00/lvol9
We have:
-rw-rw-r-- 1 root sys 0 Aug 14 09:26 /dev/vg00/lvol9
Obviously the contents of the file are AWOL.
Anyone suggest a way to recover the file ... only option I can think of is to recreate the lvol and then restore from a backup?
TIA
Simon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 09:52 PM
тАО08-13-2006 09:52 PM
Re: touch on /dev/vg00/lvol9
are you sure that is all that happened?
1. The file is still owned by root. So the user who did this had root access ?
2. I have just tried to recreate the problem and the touch command does not change the file format, only the date, as the file already exists.
So did the user delete the file first and then try to cover up with touch?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 09:57 PM
тАО08-13-2006 09:57 PM
Re: touch on /dev/vg00/lvol9
A colleague has suggested running mknod with the correct arguments but is at a loss as to the correct arguments. Our HP/UX guru is on honeymoon, so uncontactable!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 09:58 PM
тАО08-13-2006 09:58 PM
Re: touch on /dev/vg00/lvol9
To recreate the file:
rm /dev/vg00/lvol9
mknod /dev/vg00/lvol9 b 64 0x000009
(Make sure it is 5 0's followed by a 9)
then just make sure th eperms and ownership are ok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 10:06 PM
тАО08-13-2006 10:06 PM
Re: touch on /dev/vg00/lvol9
mknod /dev/vg09/group c 64 0x090000
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 10:12 PM
тАО08-13-2006 10:12 PM
Re: touch on /dev/vg00/lvol9
It is not the group file that has been whacked, but the lvol9 device file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2006 11:17 PM
тАО08-13-2006 11:17 PM
Re: touch on /dev/vg00/lvol9
To recreate the file:
delete the file
rm /dev/vg00/lvol9
create the block file
mknod /dev/vg00/lvol9 b 64 0x000009
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:02 AM
тАО08-14-2006 12:02 AM
Re: touch on /dev/vg00/lvol9
;^)
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:23 AM
тАО08-14-2006 12:23 AM
Re: touch on /dev/vg00/lvol9
melvyn burnard is goog solution.
Verify also /dev/vg00/rlvol9
Sample output "touch":
No "root" user,
$ touch /dev/vgxxxx/lvxxxx
touch: cannot change times on /dev/vgxxxx/lvxxxx
With "root" user,
#ll /dev/vgxxxx/lvxxxx
brw-r----- 1 root sys 64 0x190001 Aug 23 2004 /dev/vgxxxx/lvxxxx
#touch /dev/vgxxxx/lvxxxx
#ll /dev/vgxxxx/lvxxxx
brw-r----- 1 root sys 64 0x190001 Aug 14 14:16 /dev/vgxxxx/lvxxxx
#chmod 644 /dev/vgxxxx/lvxxxx
#ll /dev/vgxxxx/lvxxxx
brw-r--r-- 1 root sys 64 0x190001 Aug 14 14:16 /dev/vgxxxx/lvxxxx
#chmod 640 /dev/vgxxxx/lvxxxx
#ll /dev/vgxxxx/lvxxxx
brw-r----- 1 root sys 64 0x190001 Aug 14 14:16 /dev/vgxxxx/lvxxxx
rgs,
ran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:47 AM
тАО08-14-2006 12:47 AM
Re: touch on /dev/vg00/lvol9
Once you fix the missing lvol9, run the vgdisplay command. It should not report any errors. Also try mount -a which should report that all mountpoints are already mounted. Then look over all the commands in .sh_history for anything that changes the system (touch rm mv chmod chown vi, etc)
Bill Hassell, sysadmin