I have two volumes, both with 800GB total used on them. lets call them /vol1 and /vol2. /vol2 is just a cron'd rsync'd copy of a folder on /vol1 which is a live share for many users.If I temporarily suspend the cronjob doing the rsync's from /vol1 to /vol2, is it safe to unmount and e2fsck /vol2, then remount it somehow?
Both /vol1 and /vol2 say the filesystem state is not clean when i do a tune2fs -l on them both. According to tune2fs both will check themselves upon restart, but if I can do /vol2 since it isn't the live data beforehand, that will cut my downtime in half the next time i restart the server.But I also wonder that if I can do this, then i remount /vol2, will the "not clean"-ness of /vol1 just be rsync'd back over to /vol2 the next time the rsync runs?
HP 210 Mini Fedora 14 xfce 2.6.35.11-83.fc14.x86_64
I have inserted my handy drive. However, when I right click and select unmount I get the following message:
An application is preventing the volume "New Volume" from being unmounted
So I try from the command line:
umount /dev/sdb1
And I get the following message:
umount: /media/New Volume: device is busy.
All I have done is copied some files to my handy drive. So I am not sure what process is keeping my handy drive busy.Is there any command that I can use to see what process of anything else is using the handy drive?
I know if I do a shutdown -rF now, it will perform an e2fsck on all my volumes with the -y switch. But if I just want to check one of the volumes rather than all of them, and have it use the -y switch so it will automatically answer yes to everything, how can I do that?I'm using RHEL, and have a huge volume I need to run a check on, and I dont want to sit there for the next 24 hours hitting the Y key every time it finds a problem ;-)
We had to reboot a server in the middle of a production day due to 99% iowait (lots of processes in deep sleep waiting for disk iops). That's never happened to us before. It had been 363 days since the last fsck, so it started automatically on reboot. It hung at 4.8% on a 2TB LVM2 volume for about an hour. I killed the fsck and rebooted the server. The second time, it went past that point and is currently at about 62%. First, what causes e2fsck to hang like that? Second, is there any danger in killing e2fsck, rebooting, and starting it again?
I have a volume on my server that according to tune2fs is "clean with errors", so i'm assuming I either need to unmount the volume and e2fsck it, or reboot and drop into maintenance mode and do itThere aren't any live samba shares off that volume, so i'm thinking I could do it without taking the server down, as this server is only for samba shares, which are on a different volume.Could someone tell me if I'm taking the right approach? I've never done unmounting and mounting before, but I've read it can be done manually without affecting how the volumes are mounted when a server starts. i'll have to look up the commands.
Other than when there are errors in the messages log or when you have file system problems, when should you e2fsck volumes? I have a lot of volumes that have 500GB to 1TB of data on them, and it takes quite a while to e2fsck them, so wondering if its something that should be done regularly, or only when there are actually problems.
Why does an e2fsck restart itself after a while, does it get to a certain number of errors than has to start over from the beginning? are there any tweaks or switches you can use to make it run more efficiently?
I have a Debian OS installed (6.0), installed on a single partition, which was running out of space. So I copied all the data in /home to a spare partition, then edited fstab to mount this new partition as /home.
This works fine. But now of course I have the /home data both on the new partition (the one that is now being mounted and used), and also still on the original partition, though this directory is no longer mounted by the OS, so I can't directly 'get at' the data to delete it.
I could easily get into the partition from another OS and delete the unneeded /home data of course but I was just wondering; as this data is no longer 'seen' by the OS, will it be overwritten automatically by the OS when it needs more space, as it does with data that has been deleted from the filesystem, or would it be reserved somehow, still using up space?
If I umount both of them, can I run an e2fsck on each at the same time through 2 putty sessions, or will that not really gain me anything from doing them one after another?
How can I see all the physical hard drives on my Ubuntu system — regardless of whether they're mounted — as well as their partition info, sizes, &c.? I have three physical drives, but only one seems to be mounted. I'd like to mount the other ones too, as I have some data on them.
I have a heavily used file server that I want to restart, then if it requires e2fsck's on any volume to run them after it restarts. The only problem is that the server is rarely rebooted, and they said it might kernel panic because its been so long. I've heard there's a way to have it go past the kernel panic if it does happen, but I'm not sure how to do that or the other stuff.If it was a Windows server, I would schedule a shutdown with the force switch, and have the chkdsk's already scheduled for each volume on reboot. But for RHEL, I really don't know.I'm hoping this can be done, so that way I can have it kick off at say 7am, then when I get in at 8am it will probably be near the end of the e2fsck's so I can see what's going on.
I want to perform an e2fsck with the y switch (so I dont have to answer yes to every question) on two volumes on a server the next time I restart it. I don't want to do a shutdown -rF because 1) I dont want to check the other volumes and 2) it seems when I do that, the e2fsck doesn't keep restarting itself over and over to fix all the problems. Seems like it runs once, then if it fails it drops you to the repair console in single user mode. I'd rather just have it start the check that will keep repeating over and over right away, because I know it'll take more than one pass.
I have been setting up my laptop as a dual boot with Win7 (yuckkk!) and Ubunutu 11.04. My HP Pavilion dm4 came with 4 primary partitions used by Windows! (Again, yuckkk!) I got rid of Windows_recover partition (I don't remember the exact name) converted that primary partition to an extended partition and then installed Ubuntu in virtual partitions. All that works.What I don't like is that the partition HP_TOOLS shows up in Nautilus, and if you click on it, it self-mounts and makes that partition accessible.
I'm using some software that using mount point such as truecrypt. I also mount shared folder on other machine (fileserver) and publish it using ftp. The problem is when the truecrypt volume dismounted or the shared folder mount point loosing connection to the fileserver, user can write to the mount point without knowing that they actually not writing to the truecrypt volume or to the shared folder.
My question is, when sometime the server reboot and truecrypt volume is not mounted yet, how to prevent write to the mount point? I dont run truecrypt mount automatically for security reason.Some question for shared folder, if fileserver restart and the shared folder mount point got disconnected, how to prevent write to the mount point?
If I issue a shutdown -rF now, it will force e2fsck's on all the volumes when it reboots. But once the checks automatically finish, does it restart normally? I want to run e2fsck's on all my volumes, but dont want to stay the probably 5 hours it will run, so hoping someone knows for sure what happens.
I know there are many threads about recovering damaged superblocks. I've spent 3 evenings reading them and trying what they suggest. Invariably the commands do nothing except to report bad or missing superblocks. I've removed the physical disk from the machine and am working with a dd image file (/mnt/image). I can mount what used to be hdc1 and read its files with no problem. I'm trying to recover partions hdc6 and hdc7.$ mmls /mnt/image -b
DOS Partition Table Offset Sector: 0 Units are in 512-byte sectors
I've searched high and low, and can't figure this one out. I have a older Olympus Camera (2001 or so). When I plug in the USB connection, I get the following log output: $ dmesg | grep sd [20047.625076] sd 21:0:0:0: Attached scsi generic sg7 type 0 [20047.627922] sd 21:0:0:0: [sdg] Attached SCSI removable disk
Secondly, the drive is not mounted in the FS, but when I run gphoto2 I get the following error: $ gphoto2 --list-config *** Error *** An error occurred in the io-library ('Could not lock the device'): Camera is already in use. *** Error (-60: 'Could not lock the device') ***
What command will unmount the drive. For example in Nautilus, I can right click and select "Safely Remove Device". After doing that, the /dev/sg7 and /dev/sdg devices are removed.
Some things I've tried already are sdparm and sg3_utils, however I am unfamiliar with them, so it's possible I just didn't find the right command.
# mount | grep sdg # mount | grep sg7 # umount /dev/sg7 umount: /dev/sg7: not mounted # umount /dev/sdg umount: /dev/sdg: not mounted # gphoto2 --list-config
*** Error *** An error occurred in the io-library ('Could not lock the device'): Camera is already in use. *** Error (-60: 'Could not lock the device') ***
I have a dell PE1750 server which would not boot up after a power failure. I am thrown to a shell for maintenance after showing an error in file system check. The server was running - Red Hat Enterprise Linux AS release 3 (Taroon). Please let me know if I can try to recover from this error by booting from the 1st CD of a higher version of linux like RHEL5. I ask this because I do not have the old media with which the system was setup. Can the use of latest OS CD cause any problem?
I'm rearranging a bunch of disks on my server at home and I find myself in the position of wanting to move a bunch of LVM logical volumes to another volume group. Is there a simple way to do this? I saw mention of a cplv command but this seems to be either old or not something that was ever available for linux.
I've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
Typically when I'm given a SAN attached to one of my servers i'm not given any information on it. Usually I can get my with an fdisk -l to tell me what's out there. Twice now I've had to ask what the connection device is. What command can be run other than fdisk -l, I've seen something ran people by another guy but was not able to write it down at the time and have forgotten it.
I have Squeeze (2.6.32-5-686) installed on sda and have an additional disk sdb.For some reason 'dmesg' gives me always this message for sda1 (after a reboot):
Feb 14 12:29:03 arkiv-x kernel: [ 448.349949] EXT3 FS on sda1, internal journal Feb 14 12:29:03 arkiv-x kernel: [ 448.470411] loop: module loaded Feb 14 12:29:03 arkiv-x kernel: [ 448.653327] kjournald starting. Commit interval 5 seconds
I have lots of HDD on my PC and I just mount them to access files, I am wondering if these drives are turned off when unmounted? because I want to remove them physically on my computer unplug its IDE and power cable while ubuntu is running, wont it damage the drive even if its unmounted?
I just upgraded from Karmic to Lucid and have the following problems:
(1) My unmounted partitions used to be visible in "Places" on the left of Nautilus, so I could mount them when needed, but now they are not there. Also,they do not show in "Computer" view (2) When I open Disk Utility from System/Administration, there is nothing at all showing - it takes quite a while to start up, but when finally the window opens, no devices or partitions are shown.
On my desktop, I try to instantly put some disks into sleep using hdparm, for some tests. Though the disks are unmounted, they wake back up in seconds. How can it be? How can I track which process wakes a disk up with what operation? I think unmount disks should default to standby during system load.
I have two internal disks that are accessible from my ubuntu. I installed ubuntu using wubi, and those two disks are the same disks I use on Windows. One of the disks contains windows system files.These disks were easily accessible from ubuntu, I could mount/unmount anytime I wanted and had no problem with editing files. I did something I can't remember, I was just following some instruction trying to solve problem with my SD card reader. turned out it wasn't the right solution (but I fixed the SD card issue using some other instruction).
Under KDE (3.5) in Lenny, whenever I "safely remove" a SD card, I get the following message "The device was successfully unmounted, but could not be ejected" The message is obviously ridiculous, and the crashing windows error sound that accompanies it very annoying.
