I want to know what file system there are for "/dev" directory??apparently different types was developed for managing devices on Linux.because I am a little confused about all file system on this directory.Another question is,which is file system sufficient for managing devices on Embedded Linux ?of course on our embedded system we do not have many pluggable device,so this directory can be static
View 2 RepliesI need to backup my home folder (and a few other folders) on an organizational Linux NFS system where my account will be expiring soon, onto a personal hard drive (which is not using a Linux filesystem). I access the account through SSH and SFTP. I want to backup all metadata for these files and directories and everything in them, including dates, owners, groups, UID/GID numbers, CHMOD permissions, etc. How can I go about doing this? Do I need to run the LS command recursively on the directory with certain settings of what information to display, and pipe the results to a file so that the information will be in a file regardless of which filesystem I move it to? Or is there a way to save all the metadata using something like TAR/GZ? If it's with TAR/GZ, then how do I view this metadata on other filesystems that I move the archive to, and will the users/groups stored remain intact as long as it's not extracted?
In addition, do you know how to do this for SELinux metadata and AFS (Andrew File System) metadata too? (These will be for another filesystem later on, but if don't know the answer to either of these, please still answer the above.)
My ubuntu stops when mounting system hdd. The screen display the following messages :
mountall:/etc/fstab: No such file or directory fsck from util-linux-ng 2.16 WARNING: couldn't open /etc/fstab: No such file or directory init: mountall main process (545) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. udevd[560]: can not read '/etc/udev/rules.d/z80_user.rules. Ubuntu: clean, 474879/24231936 files/28016581/96898047 blocks root@i7:~# exit_
I suspect the disk manager pysdm that i had just installed today and it had crash during the previous session. The /etc/fstab file does not exist anymore and i cant rename the fstab.bak because the disk is read-only even for my root user
I have some errors when run the mount -all command: mount: wrong fs type, bad option, bad superblock on /dev/sdc5, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Failed to open /proc/filesystems: No such file or directory
[Code]..
I'm now using Ubuntu 10.04 with ext4 and for the second time in my life I experienced data loss (not for real: I got backups) and I'm assuming problems with the recent ext4 fs.
I want to restore all of my configurations (/etc and the like), data and home on reiserFS: is this possible? What to do in order to accomplish that?
I am tired of watching fsck check my filesystem when my eeepc 901 shuts down abruptly due to a crash. I know that with a journaling filesystem, I won't have to wait for a check. However, I am well aware of the poor I/O performance of the SSD, so I can imagine using a journaling filesystem being even more frustrating, since there will be constant writes to the journal? I will buy a new laptop without such a crummy ssd someday but, is there anything I can do now, on the software side of things?
View 3 Replies View RelatedI need to combine 6 different filesystems into one filesystem using rsync. I am so confused as to which parameters I need to use. The 6 fileystems are:
/mnt/tkpkgc1a/vol/mn_pkg_08_02/
/mnt/tkpkgc1a/vol/mn_pkg_08_01/
/mnt/tkpkgc1a/vol/mn_pkg_06_09/
[code]....
I accidentally unmounted filesystems using umount -a command.How to recover from this.
View 4 Replies View RelatedI have many disks and volumes in my system. Some of disks IDE, some SATA.
Volumes on SATA disks cause me problems - I have them listed in etc/fstab, but on every boot, they have different name:
/dev/sdd* becomes /dev/sdb*
/dev/sde* becomes /dev/sdc*
etc. on every boot.
1) Why is this happening?
2) How can I prevent it?
3) If I can't, is there a workaround?
When I try to start up 9.10 I can get past GRUB but not fsck. A file check will be started but no progress will be made and finally I get the 'General error mounting filesystems'.Trying in recovery mode I get this just before the fsck check
Quote:
fsck from util-linux-ng 2.16
[8.016378] ACPI: I/O resource piix4_smbs [0xb00-0xb07] conflicts with ACPI region SOR 1 [0x0b00-0xb0f]
/dev/sda1 goes fine
Quote:
/dev/sda3 has been mounted 34 times without being checked, check forced
mountall: canceled
[Code]...
This seems to be slightly different than the other threads I've seen discussing this issue. It just all of a sudden happened, I didn't upgrade anything or have any crashes immediately prior.
I want the filesystem of my external drive to be checked periodically after a numer of mounts. I put 2 in the sixth colums of fstab for this partition
Code:
/dev/sdb1/mnt/hdext3rw,dev,sync,user,noauto,exec,suid02
and I use the tune2fs to set the maximum mount count to 32.
Code:
tune2fs -c 32 /dev/sdb
now the mount count is 34 and the date of the last check is not recent, so apparently the auto fsck has not been performed. Probably because this partition is not mounted at start-up but I usually mount it manually.
I've read the first 40% of the RHEL 5 Logical Volume Manager Administrator's Guide, but still have one outstanding, burning question.
During the installation of Centos 5.6, I set up LVM physical volumes, volume groups and logical volumes. I can list these using pvdisplay, vgdisplay and lvdisplay commands.
How would I list what filesystems I have that are using my logical volumes?
We are about to install some RHEL5 servers for DB and web and Application servers. I've been asked to test which file systems of the following work better for disk I/O.EXT3 EXT4 JFS BtrFS and any other ones that I can find that work under RHEL the out-of-box install I have done allows me to format my volumes with EXT2/3 but not ext4 or any others. Is it possible to "install" other filesystems for use, if so how?
View 4 Replies View RelatedI know I can simply create a degraded raid array and copy the data to the other drive like this: mdadm --create /dev/md0 --level=1 --raid-devices=2 missing /dev/sdb1
But I want the specific disk to keep the raw ext3 filesystem so I can still use it from FreeBSD. When using the command above the disk will be a raid disk and I can't do a mount /dev/sdb1 anymore. A little background info. The drives in question are used as backup drives for a couple of Linux and FreeBSD servers. I am using the Ext3 filesystem to make sure I can quickly recover the data since both FreeBSD and Linux can read from that without problems. If someone has a different solution for that (2 drives in raid 1 that are readable by FreeBSD and writeable by Linux),
I have a 500GB external drive I want to use on a couple of Linux systems, and looking for a filesystem for it. External drives are frequently formatted in FAT32, but I don't need to interoperate with Windows and would rather avoid the ugly limited kludge that is FAT.
Since I only need to use it on Linux, I would use ext4 or XFS, but they store ownership information. Ideally, I'd use a proper Unix file system that doesn't track ownership (files are owned by whoever mounts the device, like they are when mounting a FAT32 partition), but I do not know of any file system that does that.What would be a good file system for this disk?
Is there any way to know which process had created any file in Linux Red Hat/CentOS 5?
View 2 Replies View RelatedIn a performance test, I want to bypass the influence of cache of linux system (including page cache/inode cache and so on). I have tried O_DIRECT flag, but it's turned out that direct I/O is still "enjoy" the effect of some cache.Is there a thorough way to close the effect of system cache?
View 2 Replies View RelatedIs it possible to write/edit files on HFS+ drive from Linux? Yes I need to disable journaling but how can I disable journaling from Linux? I dont have access to mac.
Or any tool available for doing this?
I am using disk utility to partition an external hard disk. My intention is to boot linux off of the partition. However, I am unsure of which format to make the partition. Disk Utility in OS X only allows Mac OS X Journaled, Mac OS X, FAT, exFAT, and free space. Which one should I use?
View 2 Replies View RelatedI've been using *Unix systems for many years now, and I've always been led to believe that its best to partition certain dirs into separate FileSystems, off the main root FS.
For instance, /tmp /var /usr etc
Leaving as little as possible on the main / system.
Its so that you don't fill up the root system be accident, by some user putting in too bigger files in /tmp, for example.
I would presume that filling the / system would not be too good for Linux, as it would not be able to write logs and possibly other things that it needs to.
I believe that if root gets full, then there is something like a 5% amount saved for just 'root' to write to, so that it can do its stuff.
However, eventually, / will become full, and writes will fail.
On top of this, certain scripting tools, such as awk, use the /tmp/ system to store temp files in, and awk wont be able to write to /tmp/ as its full, so awk will fail.
However, I'm being advised that there is no need to put /tmp /var etc onto separate FSs, as there is no problem nowerdays with / filling up. So, /tmp /var /usr are all on the root FS.
I'm talking about large systems, with TBs of data (which is on a separate FS), and with a user populations of around 800-1000 users, and 24/7 system access.
I have a bunch of disk images, made with ddrescue, on an EXT partition, and I want to reduce their size without losing data, while still being mountable. How can I fill the empty space in the image's filesystem with zeros, and then convert the file into a sparse file so this empty space is not actually stored on disk?
For example:
> du -s --si --apparent-size Jimage.image
120G Jimage.image
> du -s --si Jimage.image
121G Jimage.image
This actually only has 50G of real data on it, though, so the second measurement should be much smaller.
This supposedly will fill empty space with zeros: cat /dev/zero > zero.file rm zero.file But if sparse files are handled transparently, it might actually create a sparse file without writing anything to the virtual disk, ironically preventing me from turning the virtual disk image into a sparse file itself. :) Does it? Note: For some reason, sudo dd if=/dev/zero of=./zero.file works when cat does not on a mounted disk image.
One of the good points of linux is that is easy to customize the partitioning scheme of the disk and put each directory (/home, /var, etc) in diferent partitions and/or diferent disk. Then we can use diferen file system/configurations for each of them for make them better. xamples:
noatime is a mount option to not write access time on the files. data=writeback is an option to layz write metadata on new files. ext3/4 has journaling that make the partition more secure in case of a crash. bigger blocks make the partition waste more space, but make it faster to read and may become more fragmented. (not sure) Then: What are the best filesystem/configurations for each directory? Note: given the answer of Patches, will only discuss /, /home and /var only.
/var -> It's modified constantly, it write logs, cache, temporal, etc.
/home -> stores important files.
/-> stores everything else (/etc and /usr should be here)
/media/A and /media/B should be identical, but I want to confirm before deleting one.
Duplicate file finders don't work, because they'll find two copies of the same file within B, for instance. I only want to confirm that every file in one is identical to the other.
diff -qr /media/A/ /media/B/ seems to work, but the output is cluttered with garbage like
diff: /media/A//etc/alternatives/ControlPanel: No such file or directory
and
File /media/A//dev/tty8 is a character special file while file /media/B//dev/tty8 is a character special file
I can suppress the former with 2> /dev/null, but I don't know about the latter.
rsync -avn /media/A/ /media/B/ also produces a bunch of clutter, like "skipping non-regular file".
How can I compare the two trees and just make sure that all the real files exist in both and are identical?
I need to monitor my filesystems and get an email when the status is warning >=80 and critical >=90. I am not very good for scripting so I found an script but is not working for me This Red Hat Enterprise 5.0
Script
Code:
ADMIN="me@somewher.com"
# set alert level 90% is default
ALERT=90
df -H | grep -vE '^Filesystem|tmpfs|cdrom' | awk '{ print $5 " " $1 }' | while read output;
do
[Code]....
It's been years since I've set up a Linux machine and I am getting a "no valid devices were found on which to create new filesystems" during a Centos install on a Asus P5BV-C/4L motherboard. I am assuming that there is a raid driver that needs to be installed, but when I went to the asus download site, selected linux/P5BV-C/4L and downloaded all of the available drivers, I keep getting errors saying "Driver disk is invalid for this release of Centos".
I take the zip file, extract it down to the .img file, burn it to disk and try to load it after running a "linux dd". Is this the correct way of doing it? Am I using the correct file?
Is there some file in Linux that enumerates and describes mount options for file systems like /etc/services describes ports?
View 2 Replies View RelatedMy home server runs Debian Lenny, and I'm about to upgrade the system drive to a larger drive.In the process, I want to take the opportunity to reorganize the partitions and resize them. For learning purposes, I'm planning to migrate from an MBR partition table to GPT.Because of those two changes, I can't just run "dd if=/old/drive of=/new/drive" (well, not without lots more work afterwards). I could use the debootstrap process to get a fresh installation on the new system drive, but I used that technique during the last system upgrade and it's probably overkill for this.Can I just copy the partitions from the old drive to the new?Will "dd if=/dev/hda1 of=/dev/hdb2" work, assuming /dev/hdb2 is larger than /dev/hda1? (If so, the filesystem can be resized to take advantage of the new larger partition, right?)Would parted (or gparted) be a better tool for copying the contents of the partitions?
View 3 Replies View RelatedOriginally posted in Launchpad yesterday [Question #129083]:
Quote: System froze in mid-upgrade from 10.04 to 10.10 and now fails to boot, giving a 'general error mounting filesystems' message when loading [in either normal or recovery mode.] However, the boot menu remains accessible with the F8 key and is functional.
While in the 10.10 Live CD, using the chroot method in the grub2 help proved unsuccessful and returned this pastebinned result. The system is 10.04 64-bit running an nvidia card and sporadically froze with increasing frequency. No resolution to the freezing could be found online, which seemed associated with any of nvidia, usb, flash or even firefox. Can someone suggest an alternative to restore to bootable condition and resume upgrade without having to reinstall and wipe the drive? I also followed the copy alternative to the chroot method in the grub2 help and still get the same core dump for chroot and device not found error for upgrade-grub as posted in pastebin. I'm still running off of the 64-bit 10.10 Live CD.
Skimming other "general error mounting filesystems" topics in this section, I realise I may have to bite the bullet and cut my losses, since those other users seemed to settle for a reinstall. Any final advice out there I can try out?
I need commands which five me the following details abt all the file systems mounted the linux box
type
mount pt
file system id
I'm getting this error on boot of Mint 9 64bit. It gets to the grub boot screen (dual boot - Mint 9 32 & 64 bit) and I can boot into the 32 bit version, but the 64 bit results in that error. If I go into the maintenance shell & try fdisk -l, I get: fdisk: error while loading shared libraries: libuuid.so.1: cannot open shared object file: no such file or directory
View 4 Replies View Related