similar to: Q for folks using Samba with XFS

Yeah, I tried that but ran into a problem.? It came up fine in single-user/maintenance mode. ? The mount command shows all of the mounted file systems, but after I 'chroot /sysroot', the mount failed (with some problem with mtab, sorry don't have the exact error message).? So I couldn't mount my 32TB RAID (where the xfsdump file was). On 5/13/2020 12:48 AM, Simon Matter via

I'm having some difficulty finding a method to shrink my /home to expand my /.? They both correspond to LVMs.? It is my understanding that one cannot shrink a xfs filesystem.? One must back it up (xfsdump), remove (lvremove) redefine it and then restore it back (xfsrestore). Okay, I'm running into a problem where /home? needs to be "unused".? If tried going in to

I'll try that...I was using instructions I found on the internet for single-user/maintenance mode.?? From the grub screen you enter 'e' and modify the linux16 line...etc. Okay, I'll try that next. Thanks Simon! On 5/13/2020 7:28 AM, Simon Matter via CentOS wrote: > Hi, > >> Yeah, I tried that but ran into a problem.? It came up fine in >>

Greetings, I have a 500Gig hdd with and XFS filesystem created by openfiler (which strangely switched from lovely CentOS for reasons best known to them). I fired up a Centos box with this hdd. I then did yum install kmod-xfs.i686 xfsdump.i386 dmapi xfsprogs and it wnt through. But when I try to mount this volume mount -t xfs /dev/hdd1 /mnt/test I get the error: mount: /dev/hdd1 already

Hi All, I have this very odd issue where after a migration we have some users who have quotas showing 8192.0EB in use, when in reality on disk there is only a couple hundred megabytes. The host in question is a: * CentOS 6.3 host with mostly latest patches (except latest glibc patches) * running in SELinux Enforcing mode (Permissive doesn't seem to help) * all file systems are on Logical

Here is what installs: apt-get install sernet-samba-ad Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libdm0 libfam0 libwbclient0 sernet-samba sernet-samba-client sernet-samba-common sernet-samba-libs sernet-samba-libsmbclient0

Hi, Thanks for your reply. The file system type is xfs. And I found xfsdump/xfsrestore can undo the remove. I use dd to copy the partition as one image file. How do I mount the image as read-only device? Then I can try to recover the deleted files/directory anytime. Thanks! Regards Andrew At 2020-09-16 20:36:44, "Jonathan Billings" <billings at negate.org> wrote:

I just copied a file system using xfsdump|xfsrestore At least 1 new directory had been created on the source during the xfer (took 9+hours -- 7TB), so I wanted to verify I hadn't missed anything. Using rsync: > rsync --version rsync version 3.1.0 protocol version 31 Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks,

I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the

Hi, > Yeah, I tried that but ran into a problem.? It came up fine in > single-user/maintenance mode. ? The mount command shows all of the > mounted file systems, but after I 'chroot /sysroot', the mount failed > (with some problem with mtab, sorry don't have the exact error > message).? So I couldn't mount my 32TB RAID (where the xfsdump file was). I think you

>> Hi, >> sorry I forget to specify OS. >> I'm using: >> RH 7.2 kernel 2.4.9 >> FS - XFS 1.0.2=20 >> Samba 2.2.3a >> I'm using XFS ACL, but I need set EA(ACL) to Change (read - yes, write - >> yes, delete - no, execute - no). >> I don't know how to set this with standard UNIX permissions (rwx).=20 >>

Hi, > I'm having some difficulty finding a method to shrink my /home to expand > my /.? They both correspond to LVMs.? It is my understanding that one > cannot shrink a xfs filesystem.? One must back it up (xfsdump), remove > (lvremove) redefine it and then restore it back (xfsrestore). > > Okay, I'm running into a problem where /home? needs to be "unused".? If

On 3/3/2017 5:34 AM, Robert Moskowitz wrote: > Well, I only wanted to copy the used part of the drive which I try to > keep small so I can still copy the image to an mSD card if I wish. So > I have to supply the amount of the drive to copy. The bs=512 went > fast enough, but then I was only copying 3.2GB. > > thanks for the help. personally, I would use 'dump' for

Hi, >> >> Thanks for your reply. The file system type is xfs. And I found >> xfsdump/xfsrestore can undo the remove. > >Hm, are you sure you can use xfsdump/xfsrestore for this? > xfsdump/xfsrestore can't do the recovery. >> I use dd to copy the partition as one image file. How do I mount the image >> as read-only device? Then I can try to recover

It was noted in CentOS Bug 7795 that the amanda package in CentOS does not have dump or xfsdump support: http://bugs.centos.org/view.php?id=7795 I found that it is also like this upstream and they plan to fix it at some point: https://bugzilla.redhat.com/show_bug.cgi?id=1140321 In the mean time, I have created 2 sets of RPMs .. one with dump support and one with dump and xfsdump support: Dump

I''m trying to get a new file server managed by puppet from day 1, at least as much as possible. At the moment, though, there''s two issues I''m running into: 1. fstab should have entries for my comically-large RAID, but doesn''t. 2. each puppet run appears to remount the RAID, even when no rules in the manifest change. I suspect the issue may be in parsing

CentOS Errata and Bugfix Advisory 2014:1798 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1798.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3dcc904088bb38ea8bca79e8013e3dcff6f3f3faf97670aa96519cac1e617580 xfsdump-3.0.4-4.el6_6.1.x86_64.rpm Source:

I am attempting to implement XFS on a new system. System: Supermicro SC846 TQ-R900B - rack-mountable SUPERMICRO X7DWN+ - motherboard 3ware 9650SE-24M8 - storage controller 10 Hitachi DeskStar 7K1000 - hard drive - 1 TB 8GB Ram 2 Intel Quad-Core Xeon E5420 / 2.5 GHz processor Installed Centos 5.1 X86 64 from DVD. System on /dev/sda1 ? 250GB ext3 (raid 5). /home will be on /dev/sdb1 ? over 7TB

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

patch" with star. And it is preferred to backup XFS with xfsdump. If you don't use a filesystem that understands ACLs, then Samba maintains all = the ACL info in a common file. You as the administrator are responsible for creating a backup mechanism that = captures the Samba ACL info. That is easy if you are happy with doing a full share backup/restore, but if = you want to be able to