Sponsored Content
Top Forums Shell Programming and Scripting big problem with rm command, please help me!! Post 302340717 by danmero on Tuesday 4th of August 2009 08:39:58 AM
Old 08-04-2009
Quote:
Originally Posted by Moumou
So here is my question: does anyone knows how to get back the data deleted with rm command??
  1. Restore from snapshot
  2. Restore from backup
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem editing big file in vi

I have a big file, which vi opens it with message not sufficient space with file system. I am not adding any data in the file but changing some values within. To make these changes effective, it asks for forced write (w!), even after doing this, I see this particular record, change is not... (4 Replies)
Discussion started by: videsh77
4 Replies

2. UNIX for Advanced & Expert Users

a BIG problem

dear experts ...help :eek: I'm running FC2 and i was installing fluxbox but it wouldnt work so i uninstalled it by using rpm -e but because i installed fluxbox-styles it was dependent on fluxbox-0.10 so i used rpm -e --nodeps that was all fine and im not sure that was the cause of the error, but... (1 Reply)
Discussion started by: zeeman
1 Replies

3. UNIX for Dummies Questions & Answers

kinda big problem

Hi again! I finally managed to image the 3 floppies for installing freeBSD but I simply can't boot! I've selected floppy for first boot device and it even starts to readf the boot floppy and the hard drive light is continuously flashing but it doesn't stop even after half an hour and doesn't do a... (4 Replies)
Discussion started by: Mudrack
4 Replies

4. UNIX for Dummies Questions & Answers

A Big Problem in LINUX Booting

i have some problem in linux booting will u please help me the problem is i was using federo core 1 on my system everything was fine i made one entry in /etc/fstab file for accessing E drive of WINDOWS XP in that i had given file system as VFAT after rebooting system it was not... (1 Reply)
Discussion started by: great_indian
1 Replies

5. Linux

Problem with creating big files

Hi... I have a very wired problem with my redhat4 update 4 server... Every time i create a file bigger then my physical memory the server kills the process\session that creates the file, and in the "messages" file i see this error: "Oct 21 15:22:22 optidev kernel: Out of Memory: Killed process... (6 Replies)
Discussion started by: eliraza6
6 Replies

6. Programming

please help me with this big makefile problem

I need to create an executable with these two makefiles(they both have libaries i need(qt and ruby)) i have extconf.rb gui.ui gui_include.h main.cpp ScaleIM_client.rb ui_gui.h i want to combine them all into one executable please!... (2 Replies)
Discussion started by: gjgfuj
2 Replies

7. Shell Programming and Scripting

[newb] simple script, big problem

Warning! I'm ridiculously new at all this, so pardon my ignorance... I have a very simple script which is intended to search a hosts file when given a partial hostanme or ip address. The if the partial hostname/ip given is unique, the script automatically logs the user in to that host. If... (6 Replies)
Discussion started by: itomb
6 Replies

8. Post Here to Contact Site Administrators and Moderators

Big problem during the access for the password

Every time that i quit from the forum despite i'm 100 % sure that i put the right login (i make a copy and past of the correct data) i obtain always the message that the login is wrong so i must always reset it. :wall: Could be a bug? I use a 64 bit linux system. (4 Replies)
Discussion started by: alexscript
4 Replies
vgcfgrestore(1M)														  vgcfgrestore(1M)

NAME
vgcfgrestore - display or restore LVM volume group configuration from backup file or kernel memory SYNOPSIS
vg_name vg_name old_pv_path] pv_path vg_conf_path vg_conf_path old_pv_path] pv_path pv_path Remarks cannot be performed if the volume group is activated in shared mode. cannot be performed on devices attached to activated volume groups. Prior to restoring a backup configuration to a disk, detach the physi- cal volume from the volume group using the command (see pvchange(1M)), or deactivate the volume group using the command (see vgchange(1M)). will refuse to restore a configuration to a physical volume with a block size different than the block size stored in the configuration backup file for that physical volume. DESCRIPTION
The command restores the LVM configuration data from a default option) or alternate option) configuration backup file, or from kernel mem- ory option), to the physical volume named by pv_path. Or, it displays the configuration data on standard output option). The configuration stored for one physical volume, old_pv_path, can be copied to another physical volume pv_path option). Options and Arguments recognizes the following options and arguments: pv_path The raw (character) device path name of a physical volume that is currently online. If the option is omitted, pv_path must specify a physical volume whose configuration is stored in the configura- tion backup file. Get configuration information from the alternate configuration backup file vg_conf_path. This option is applicable to input arguments belonging to volume groups version 1.0. Forcibly restore the LVM configuration data even if the physical volume has alternate block(s) allocated inside the user data area. This option should be used with extreme caution. User is advised to fix the problem because potential data corruption could occur. Get configuration information from LVM data structures in kernel memory. The volume group containing pv_path must be activated in order to use this option. List the configuration information saved in the specified configuration backup file. Get configuration information from the default configuration backup file: vg_name is the path name of the volume group. base_vg_name is the base name of vg_name. For example, if vg_name is specified as base_vg_name is Restore the configuration information saved for physical volume old_pv_path to physical volume pv_path. This option is useful when a physical volume's name has changed since the configuration backup file was created or updated. old_pv_path must be the path name of a physical volume whose configuration is stored in the configuration backup file. It needs not be currently online. pv_path must be the path name of a physical volume that is currently online. Its configuration needs not be stored in the configuration backup file. Forcibly restore the LVM configuration data even if there is a physical volume mismatch between the kernel and the configuration backup file with the volume group still active. This option should not be used unless the configuration file is absolutely valid and up-to-date. Restoring invalid configuration data can result in data corruption later. If there are alternate physical volume links configured in the system, the following message will appear when total number of physical volumes in the kernel does not match with the configuration backup file due to missing alternate physical volume links: Mismatch between the backup file and the running kernel: Kernel indicates X disks for /dev/vgname; /etc/lvm- conf/vgname indicates Y disks. Cannot proceed with the restoration. Deactivate the Volume Group and try again. In this case, the user is advised to deactivate the volume group first, then use the command to restore configu- ration data when the volume group is unavailable. But if the volume group has to stay available and the user is absolutely sure the configuration file is correct, this option will restore data from the configuration file when the volume group stays available. Provide additional information when invoked together with option. o Additional values displayed for each path: o Disk size in kilobytes o Starting block number (kb) of the user data. o The PVkey (see Note that paths with the same key are links to the same device. Additional values displayed for each volume group: o max_pv o max_pe o max_lv o vg_version o vg_size (only volume groups version 2.0 or higher, see vgcreate(1M)) RETURN VALUE
exits with one of the following values: Successful completion. Failure. Errors occurred during the restore operation. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Restore the LVM configuration information for the physical volume that was saved in the default file Force to restore the LVM configuration data when volume group is still active: Restore the LVM configuration information to physical volume using alternate configuration file List backup information saved in default configuration file Above command might display the following: Restore LVM configuration information stored for in default configuration file to physical volume Restore LVM configuration information to physical volume using LVM data structures in kernel memory. The volume group containing must be activated: AUTHOR
was developed by HP. SEE ALSO
pvchange(1M), vgcfgbackup(1M), vgchange(1M), intro(7), lvm(7). vgcfgrestore(1M)
All times are GMT -4. The time now is 02:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy