similar to: Can't delete or move /home on 7.3 install

On 12/15/2016 01:47 AM, Gianluca Cecchi wrote: > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III < > replicant at dallaslamers.org> wrote: > >> Tried this in both AWS and GCE as I though it may be a specific cloud >> vendor issue. SELinux is disabled, lsof | grep home shows nothing, >> lsattr /home shows nothing. Simply get "Device or resource

Jon LaBadie wrote: > On Thu, Dec 15, 2016 at 04:10:07AM -0600, geo.inbox.ignored wrote: >> On 12/15/2016 01:47 AM, Gianluca Cecchi wrote: >> > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III < >> > replicant at dallaslamers.org> wrote: >> > >> >> Tried this in both AWS and GCE as I though it may be a specific cloud >> >> vendor

I was most def root. /home isn't mounted as a separate filesystem. It's not even tmpfs or btrfs. I was able to boot into single user mode to remove it, but this isn't possible in an automated fashion. I may just have to start building my own images. Still curious to know why I can't rename or move it. Anyone else try this on a stock 7.3 build? On Thu, Dec 15, 2016 at 8:42 AM,

On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III < replicant at dallaslamers.org> wrote: > Tried this in both AWS and GCE as I though it may be a specific cloud > vendor issue. SELinux is disabled, lsof | grep home shows nothing, > lsattr /home shows nothing. Simply get "Device or resource busy." > > Works just find on 7.2 so I'm kinda at a loss. Scanned

On Thu, Dec 15, 2016 at 04:10:07AM -0600, geo.inbox.ignored wrote: > > > On 12/15/2016 01:47 AM, Gianluca Cecchi wrote: > > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III < > > replicant at dallaslamers.org> wrote: > > > >> Tried this in both AWS and GCE as I though it may be a specific cloud > >> vendor issue. SELinux is disabled, lsof |

Howdy, Before I go about writing one myself, anyone out there written a software inventory module/fact for gathering a list of all installed rpms/debs on a system? Got a few ideas floating around in my head, but wanted to see if/what other folks have done .. -- I''ve seen things you people wouldn''t believe. Attack ships on fire off the shoulder of Orion. I watched C-beams

On Thu, Dec 15, 2016 at 11:51:28AM -0800, Glenn E. Bailey III wrote: > Doing a lsof showed no open files against /home. Something else is > locking it, not a user process. Also disabled SELinux, did a init 1, > and only way to remove it was via single user by passing > init=/sysinit/bin/sh It sounds like /home is being managed by something in the kernel, then. Are you exporting /home

On Fri, Dec 16, 2016 at 10:17:21AM -0800, Glenn E. Bailey III wrote: > This is a base install. If you deploy an instance in ec2 or GCE (ec2 > you can do the free tier) it's easily repeatable. Even on a RHEL 7.3 > instance. Note you'll need to allow root and password logins via SSH > before attempting. I can confirm this. The culprit? NetworkManager has /home open. I

This is a base install. If you deploy an instance in ec2 or GCE (ec2 you can do the free tier) it's easily repeatable. Even on a RHEL 7.3 instance. Note you'll need to allow root and password logins via SSH before attempting. On Fri, Dec 16, 2016 at 5:47 AM, Jonathan Billings <billings at negate.org> wrote: > On Thu, Dec 15, 2016 at 11:51:28AM -0800, Glenn E. Bailey III wrote:

On Thu, Dec 4, 2014 at 8:00 AM, Dan Liew <dan at su-root.co.uk> wrote: > * Who should fund whatever host is used to host the LNT > infrastructure. Given the commercial interest in LLVM I hope that this > will be straight forward > FWIW, if you can use google's cloud offerings, I can likely fund it. This isn't about only being willing to fund our platform vs. some other

During a routine trawl through the ext3 files, I found some astronomical file sizes, billions and billions of GB. They also has strange user and group names. I can not delete these "weird files" (the term used by the operating system utilities). Here are a few examples. The original files were created on Windoze 98 version 2 circa 2001. > 2411957 p--x---rwx 65487 299196551

Hi, I get the error "Operation not permitted" when I try to delete a file as root, see some commands below. - there is no "i" attribute - it's a problem with the files and not the upper directories since I can delete a similar file in the same directory - fsck -f doesn't find any error on the partition - the partition is mounted rw If this is not the right place to

Yup, verified those options are *not* set in 7.2. For a quick test I simply removed them from /usr/lib/systemd/system/NetworkManager.service, did a systemctl daemon-reload, restarted NetworkManager, logged back in as root, and was able to whack /home (7.3). On Tue, Dec 20, 2016 at 11:07 AM, Matthew Miller <mattdm at mattdm.org> wrote: > On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan

Hi all Anyone can help to let me know how to ls -1 | lsattr ls -al /folder | awk '{ print $2}' | lsattr Thank you

Hello Glen, On Thu, 2016-12-15 at 10:10 -0800, Glenn E. Bailey III wrote: > I was most def root. There's a difference whether you logged in as root or su-ed to root. In the latter case /home is still in use by the user you su-ed from. Even though it is not strictly necessary to init 1 you must make sure not a single user that uses /home for their home directory is logged in and no system

Hi, On Tues Jul 17th, we had a full GitLab outage from 14:00 to 18:00 UTC, whilst attempting to upgrade the underlying storage. This was a semi-planned outage, which we'd hoped would last for approximately 30min. During the outage, the GitLab web UI and API, as well as HTTPS git clones through https://gitlab.freedesktop.org, were completely unavailable, giving connection timeout errors.

Hi all, I'm taking a stab at deploying a storage cluster to explore the Halo AFR feature and running into some trouble. In GCE, I have 4 instances, each with one 10gb brick. 2 instances are in the US and the other 2 are in Asia (with the hope that it will drive up latency sufficiently). The bricks make up a Replica-4 volume. Before I enable halo, I can mount to volume and r/w files. The

We run a third party application that creates an inordinate amount of subdirectories in a single directory. To speed up I/O, I wanted to set the T attribute on the directory that will hold the subdirectories. The "chattr +T /usr/local/lepus-bb/a-0607" command returns status 0, but when I verify the setting, the attribute isn't there: # lsattr -d /usr/local/lepus-bb/a-0607

I cannot access home samba share from windows. Windows client displays a permission denied error. The problem is not Linux permissions for the user directory, permission is still denied when permissions are to 777. I don't think the problem is selinux, because no denials appear in any logs. I don't think it's an extended attributes issue from xfs, because I don't see any attributes

I have searched for this topic on the mailing list and on Google without finding anything. Is this already a well known issue? The problem is that rsync does not preserve ext2-4 attributes (even when using the -a, -A, and -X flags). Note that these are different from extended attributes: Extended attributes are manipulated using programs such as getfattr and setfattr (on Unix-like systems),