search for: filesystems

On Sun, Feb 21, 2010 at 8:40 AM, Goffredo Baroncelli <kreijack@gmail.com> wrote: >       filesystem resize [+/-]<size>[gkm]|max <filesystem> -filesystem resize [+/-]<size>[gkm]|max <filesystem> +filesystem resize [+/-]<size>[gkm]|max <dev> This command works on devices, not paths. >              Resize a filesystem identified by <path>.  The

Folks, While going through a quick tutorial on zfs, I came across a way to create zfs filesystem within a filesystem. For example: # zfs create mytest/peter where mytest is a zpool filesystem. When does this way, the new filesystem has the mount point as /mytest/peter. When does it make sense to create such a filesystem versus just creating a directory? # mkdir mytest/peter Thank you in

Hi all, I want to setup a RAID storage system, where i have two systems connected to it. the filesystems are mapped out to both connectors. I want the master host mount them read write, and the slave read only. in my fstab on the slave I have a line like the following: /dev/sdb1 /mount ext3 acl,noauto,user_xattr,nosuid,ro 0 0 so in man 5 fstab, it is written, that when the 6. field is 0,...

..." /etc/sysconfig/network-script/ifcfg-p2p1 DEVICE="p2p1" BOOTPROTO="dhcp" BRIDGE="br0" NM_CONTROLLED="no" ONBOOT="yes" TYPE="Ethernet" the fstab of host # # /etc/fstab # Created by anaconda on Fri Jul 26 05:26:08 2013 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=b49ce5dc-afb7-4c8e-9487-c1ed101d9166 / ext4 defaults 1 1 UUID=3dfa07fd-a06b-4a1a-a3fd-4e2f5e0d0e6a /boot ext4 d...

Hi, Our virtual machines have some filesystem corruption problems. The filesystem is being mounted on read-only mode. When running fsck command, everything goes ok. Our configuration Dom0 : RHEL4 Update 3 Xen : 3.0.2.2, compiled from sources. Linux Xen kernel : 2.6.16 File-System : ext3 w/ LVM DomU : Fedora Core 4 ou 6 Xen : 3.0.2.2, compiled from sources. Linux Xen Kernel : 2.6.16

Hello, Just a few quick, but not very simple questions...: Do any Linux filesystems (besides XFS) support freezing? (ie. in conjuction with LVM snapshots this can allow a mounted filesystem to be frozen [freezing all processes writing to this filesystem] in a valid state (with possibly dangling unlinked files), the device can be snapshotted via LVM, and the original filesystem un...

...g=fs:ext4:2G resize2fs-size /dev/sda1 1073741824 As result, try to mount the filesystem, and get its actual statistics to determine its full size. In case mounting fails, fall back to the previous method, which is still a good value in the majority of the cases. Thanks to: Erik Skultety. --- cat/filesystems.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/cat/filesystems.c b/cat/filesystems.c index cec3c4e47..2b95d3112 100644 --- a/cat/filesystems.c +++ b/cat/filesystems.c @@ -508,7 +508,23 @@ do_output_filesystems (void) guestfs_pop_error_handler (g);...

...2560359 blocks [ok] Remounting root filesystem in read-write mode: [ok] Finding module dependencies: [ok] Checking filesystems /boot:clean,32/6024 files, 6328/24066 blocks /home:Attempt to read block from filesystem resulted in short read while reading block 523 /home:Attempt to read block from filesystem resulted in short read reading journal superblock fsck.ext3:Attempt to read block from filesystem resulted in short rea...

...org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008 jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 Note: I just cvsupped earlier, and no changes have been put into cvsup that would fix this problem. Full Description: I was doing a reorganization of my filesystems, and since I do offline installs, I keep a local distfiles collection (or did until yesterday when this happened), and in the process, put all of the distfiles on their own filesystem to be mounted under /usr/ports/distfiles. All was fine until I rebooted. On rebooting, I got a page fault pani...

...org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008 jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 Note: I just cvsupped earlier, and no changes have been put into cvsup that would fix this problem. Full Description: I was doing a reorganization of my filesystems, and since I do offline installs, I keep a local distfiles collection (or did until yesterday when this happened), and in the process, put all of the distfiles on their own filesystem to be mounted under /usr/ports/distfiles. All was fine until I rebooted. On rebooting, I got a page fault pani...

> On Aug 10, 2018, at 13:28, Marshall Clow via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > > > On Thu, Jul 26, 2018 at 9:20 PM, Eric Fiselier via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > Hi All, > > I recently committed <filesystem> to trunk. I wanted to bring attention to some quirks it currently has.

Hello, I am starting the system container without "/" directory So that it can share the host /bin /sbin /lib and /lib64 and i have sepeartely mounted /var, /etc and /usr directory for the container Below is xml file <domain type='lxc'> <name>test6</name> <memory>102400</memory> <os> <type>exe</type>

I made a filesystem (mke2fs -j) on a logical volume under kernel 2.6.20 on a 64-bit based system, and when I try to mount it, ext3 complains with EXT3-fs: dm-1: couldn't mount because of unsupported optional features (80). I first thought I just forgot to make the filesystem, so I remade it and the error is still present. I ran fsck on this freshly made filesystem, and it completed with

Hi All, I recently committed <filesystem> to trunk. I wanted to bring attention to some quirks it currently has. First, it's been put in a separate library, libc++fs, for now. Users are responsible for linking the library when they use filesystem. Second, it should still not be considered ABI stable. Vendors should be aware of this before shipping it. Hopefully all the standard and

...b/bash/virt-resize index 4471f07..5627807 100644 --- a/bash/virt-resize +++ b/bash/virt-resize @@ -36,6 +36,9 @@ _guestfs_options_only () --password-crypto) COMPREPLY=( $( compgen -W "md5 sha256 sha512" -- "$cur") ) return ;; + --unknown-filesystems) + COMPREPLY=( $( compgen -W "ignore warn error" -- "$cur") ) + return ;; esac case "$cur" in diff --git a/resize/resize.ml b/resize/resize.ml index 75bb2f7..ecb7cf0 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -149,13 +149,...

Greetings - I am going through some testing steps to expand a logical volume and the corresponding filesystem on a KVM guest and have run across a deficiency in my knowledge. I spent the afternoon yesterday googling for answers, but had have come up blank still. What I am trying to do is resize the file system to use the additional disk space that I added to the logical volume that the

hi all, I hope you can help me with a strange quota/nfs/XFS behavior... I'm using Centos 5.6 on both a nfs server and client. Both are 64-bit, and using a recent kernel: NFS server: Linux fs2.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux NFS client: Linux nx8.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64

Hope someone can point me in the right direction. I don't know if what I am trying to do should work or not. I have 2 disk images. One is a VM with an ext2 boot filesystem and ext4 filesystems with the OS loaded. I am amble to guestmount this with no issue and am able to see the files that are on the ext2 file system. I can also run guestfish on the image, mount the ext2 filesystem, and list the files. However, the second image I have is only a boot disk image with just an ext2 filesy...

Hello, This is the userspace part of restriper, rebased onto the new progs infrastructure. Restriper commands are located under ''balance'' prefix, which is now the top level command group. However to not confuse existing users ''balance'' prefix is also available under ''filesystem'': btrfs [filesystem] balance start btrfs [filesystem] balance

FWIW, I’d like for us to come to an agreement before the branch for LLVM 7.0 is cut. How do others feel about this? Am I wrong when I claim that shipping an ABI-unstable feature in the std:: namespace is a deviation from normal practice? Am I overcautious when I say it’s asking for trouble? Eric, I know you’re busy and may not have time to do the work so I’m totally willing to chime in, but I’d