I ran the following command
du --apparent-size --block-size=1 --summarize /mnt2/nfspools/_root_root_p1
PS: /mnt2/nfspools/_root_root_p1 is mount point for volume in data ontap filer.
I got the following output:
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
`/mnt2/nfspools/_root_root_p1/.snapshot/hourly.0'
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
`/mnt2/nfspools/_root_root_p1/.snapshot/nightly.0'
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
`/mnt2/nfspools/_root_root_p1/.snapshot/hourly.1'
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
`/mnt2/nfspools/_root_root_p1/.snapshot/hourly.2'
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
`/mnt2/nfspools/_root_root_p1/.snapshot/hourly.3'
16384 /mnt2/nfspools/_root_root_p1
is there any setting I can do netapp data ontap to avoid this warning when I run du command?
I figured out how to avoid this warning message.
On filer volume I ran the following command:
vol options perf_test_pool2 nosnapdir on
The above command hides the .snapshot directory when accessing volume content.
Related
I currently have the folder structure shown below.
The include file apparently does not belong, since it does not exist in an earlier cygwin directory I had backed up.
Also, I continually get this warning :
cc1plus: warning: /usr/local/include: not a directory
Should I delete this file, because I believe it is preventing an include directory from being created during builds.
This is the error message:
/home/hulukfyacom/nodevenv/myapp/10/bin/npm: fork: Cannot allocate memory
/home/hulukfyacom/nodevenv/myapp/10/bin/npm: line 13: /home/hulukfyacom/myapp/activate: No such file or directory
/home/hulukfyacom/nodevenv/myapp/10/bin/npm: line 14: /home/hulukfyacom/myapp/set_env_vars.py: No such file or directory
mkdir: cannot create directory '/lib/node_modules': Read-only file system
ln: failed to create symbolic link '/lib/package.json': Read-only file system
/home/hulukfyacom/nodevenv/myapp/10/bin/npm: line 35: /usr/bin/npm: No such file or directory
I am currently hosting my nodejs website and when I try to install npm it showed me this error. How can I solve this error please...any help...
You will need to create a symlink to your node and npm executables:
ln -s /opt/cpanel/ea-nodejs10/bin/npm /usr/local/sbin/npm
ln -s /opt/cpanel/ea-nodejs10/bin/node /usr/local/sbin/node
Not 100% sure if this is accurate since I don't have access to CPanel to test.
Although on further inpsection, it looks like you may be out of memory or even the file permissions are wrong. If the symlink does not work, can you run the following commands?
htop
If your memory is maxed out, this may be the source of your problem.
df -lh
This command will list the free hard disk space. Make sure the disk is not full.
ls -l
This will list the files and permissions, make sure that the file permissions are correct.
^These things are presuming that you have command line access. You should be able to check the resource usage from the CPanel interface if you need.
Spack by default writes (on my system) into a directory spack-stage inside /tmp/. This directory can get full when building something big (e.g. GCC itself), at least in the shared system I am using:
fatal error: error writing to /tmp/ccPlIYSg.s: No space left on device
Is there any way to tell Spack to use a different location for spack-stage?
According to the spack documentation you just need to specify $TMP to point to a directory of your choice.
Builds can be faster in temporary directories on some (e.g., HPC) systems.
Specifying $tempdir will ensure use of the default temporary directory
(i.e., $TMP or $TMPDIR).
Another option that prevents conflicts and potential permission issues is
to specify ~/.spack/stage, which ensures each user builds in their home
directory.
I need to add files to an initramfs file(I own the file as this is for some other device), however I do not have root permissions on my development machine. The usual way would be to unpack the initramfs, add files, change owner to root and pack again. I can not do this, as changing owner on this machine would require root permissions. If I do not change owner the system might behave weird(and it is just not a clean setup).
I can not do this on the target system as it is an embedded system, which only has read only access to the initramfs file.
Is there any way to change the permissions during or after packing the cpio archive?
Use fakeroot to deal with permissions during extraction and compression. it is developed to provide root environment without actually being root.
girishp#~/incoming$ /usr/bin/fakeroot /bin/bash
root#~/incoming$
We're trying to use oprofile to track down performance problems on a server cluster. However, the servers in question have a read-only file system, where /var/tmp is the only writeable directory.
OProfile wants to create two directories whenever it runs: /root/.oprofile and /var/lib/oprofile, but it can't, because the filesystem is read-only. I can use the --session-dir command line option to make it write its logs to elsewhere than /var/lib, but I can't find any such option to make it use some other directory than /root/.oprofile.
The filesystem is read-only because it is on nonwriteable media, not because of permissions -- ie, not even superuser can write to those directories. We can cook a new ROM image of the filesystem (which is how we installed oprofile, obviously), but there is no way for a runtime program to write to /root, whether it is superuser or not.
I tried creating a symlink in the ROM that points /root/.oprofile -> /var/tmp/oprofile, but apparently oprofile doesn't see this symlink as a directory, and fails when run:
redacted#redacted:~$ sudo opcontrol --no-vmlinux --start --session-dir=/var/tmp/oprofile/foo
mkdir: cannot create directory `/root/.oprofile': File exists
Couldn't mkdir -p /root/.oprofile
We must run our profilers on this particular system, because the performance issues we're trying to investigate don't manifest if we build and run the app on a development server. We can't just run our tests on a programmer's workstation and profile the app there, because the problem doesn't happen there.
Is there some way to configure oprofile so that it doesn't use /root ?
I guess it should be as simple as overriding the HOME environment variable:
HOME=/tmp/fakehome sudo -E opcontrol --no-vmlinux --start --session-dir=/var/tmp/oprofile/foo
If that doesn't work out, you could have a look at
unionfs
aufs
to create a writable overlay. You might even just mount tmpfs on /root,or something simple like that.
It turns out that this directory is hardcoded into the opcontrol bash script:
# location for daemon setup information
SETUP_DIR="/root/.oprofile"
SETUP_FILE="$SETUP_DIR/daemonrc"
Editing those lines seemed to get it working, more or less.