05-29-2001
all better
Turns out that the filesystem the target directory resides in was at 100% capacity.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a SCO UNIX on my Server. When I last tried to shutdown my system, I got an error message
“no space left on device”.
Now when I try to boot the system again, I
just can't and I get the same error message. Please help! (2 Replies)
Discussion started by: anjane
2 Replies
2. Solaris
Hi all,
A very strange problem I have this morning with my Solaris 8.
I have a FS full, I deleted some files but the system doesn't seems to reallocate the free space (I'm using Veritas):
df -k :
/dev/vx/dsk/dlds02vg/dlds02oralv 4194304 4194304 0 100% /dlds02/lds/oracle
... (4 Replies)
Discussion started by: unclefab
4 Replies
3. Solaris
We are using this function tmpfile() :
FILE *tmpfp ;
if ((tmpfp = tmpfile()) == NULL)
{
fprintf(stderr, "%s: ERROR: init_operator(): ", ROUTINE);
perror("tmpfile()");
exit(ERR_OPEN);
}
and the above is raising error :
MSMD0603: ERROR:... (3 Replies)
Discussion started by: atiato
3 Replies
4. UNIX for Dummies Questions & Answers
hello all,
i have a proc binary that we run on unix environment, and it is generating this error
'' tstfile(): No space left on device ''
can you please assist on how to narrow down the problem?
thanks (4 Replies)
Discussion started by: mjdbouk
4 Replies
5. Solaris
Hi,
During package install, am getting:
WARNING: unable to write temp contents file </var/sadm/install/t.contents>
(errno 28: No space left on device)
I tried to delete some stuff under "/var" But I cannot locate who is occupying "/var" space. Because:
# df -h /var/
Filesystem ... (5 Replies)
Discussion started by: viki250
5 Replies
6. Solaris
hi guys, me again ;)
i recently opened a thread about physical to zone migration.
My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone.
We are talking about 22mio of files.
i used rsync to do that and every time at... (8 Replies)
Discussion started by: beta17
8 Replies
7. Shell Programming and Scripting
Hi,
We are trying to sort the 40GB file in unix and getting following error.
Error:
sort: can't write /var/tmp/stmAAAvsaGfJ.00002929: No space left on device
sort -t ',' -k4 $DIR/INF_ff_FULL.dat >>$DIR/Sort_INF_ff_FULL.dat; 2>$DIR/sort_error.log
Can you please advise how to... (2 Replies)
Discussion started by: koti_rama
2 Replies
8. Ubuntu
I am running a build on Jenkins and I get:
No space left on device
But when I do df, I get:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/ROOT 19249724 18267492 4380 100% /
udev 1457152 4 1457148 1% /dev
tmpfs ... (4 Replies)
Discussion started by: sgffgs
4 Replies
9. Linux
Hello people
I have a small fileserver running busybox (very small linux distro with most essential stuff on it) and I am trying to remove some unused directories on it.
When I try this:
rm -R test/I get:
rm: cannot remove 'test': No space left on devicedf shows:
Filesystem ... (8 Replies)
Discussion started by: GTCG
8 Replies
10. Linux
Hello all
posting here after scanning the net and tried most of the things offered
still no solution that worked
when I do :
$ df -h
Filesystem Size Used Avail Use% Mounted on
footmpfs 7.9G 60K 7.9G 1% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
/dev/da1 ... (3 Replies)
Discussion started by: umen
3 Replies
LEARN ABOUT MOJAVE
xfs_metadump
xfs_metadump(8) System Manager's Manual xfs_metadump(8)
NAME
xfs_metadump - copy XFS filesystem metadata to a file
SYNOPSIS
xfs_metadump [ -efgow ] [ -l logdev ] source target
DESCRIPTION
xfs_metadump is a debugging tool that copies the metadata from an XFS filesystem to a file. The source argument must be the pathname of
the device or file containing the XFS filesystem and the target argument specifies the destination file name. If target is -, then the
output is sent to stdout. This allows the output to be redirected to another program such as a compression application.
xfs_metadump should only be used to copy unmounted filesystems, read-only mounted filesystems, or frozen filesystems (see xfs_freeze(8)).
Otherwise, the generated dump could be inconsistent or corrupt.
xfs_metadump does not alter the source filesystem in any way. The target image is a contiguous (non-sparse) file containing all the
filesystem's metadata and indexes to where the blocks were copied from.
By default, xfs_metadump obfuscates most file (regular file, directory and symbolic link) names and extended attribute names to allow the
dumps to be sent without revealing confidential information. Extended attribute values are zeroed and no data is copied. The only excep-
tions are file or attribute names that are 4 or less characters in length. Also file names that span extents (this can only occur with the
mkfs.xfs(8) options where -n size > -b size) are not obfuscated. Names between 5 and 8 characters in length inclusively are partially
obfuscated.
xfs_metadump should not be used for any purposes other than for debugging and reporting filesystem problems. The most common usage scenario
for this tool is when xfs_repair(8) fails to repair a filesystem and a metadump image can be sent for analysis.
The file generated by xfs_metadump can be restored to filesystem image (minus the data) using the xfs_mdrestore(8) tool.
OPTIONS
-e Stops the dump on a read error. Normally, it will ignore read errors and copy all the metadata that is accessible.
-f Specifies that the filesystem image to be processed is stored in a regular file (see the mkfs.xfs -d file option). This can also
happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8).
-g Shows dump progress. This is sent to stdout if the target is a file or to stderr if the target is stdout.
-l logdev
For filesystems which use an external log, this specifies the device where the external log resides. The external log is not copied,
only internal logs are copied.
-o Disables obfuscation of file names and extended attributes.
-w Prints warnings of inconsistent metadata encountered to stderr. Bad metadata is still copied.
DIAGNOSTICS
xfs_metadump returns an exit code of 0 if all readable metadata is successfully copied or 1 if a write error occurs or a read error occurs
and the -e option used.
NOTES
As xfs_metadump copies metadata only, it does not matter if the source filesystem has a realtime section or not. If the filesystem has an
external log, it is not copied. Internal logs are copied and any outstanding log transactions are not obfuscated if they contain names.
xfs_metadump is a shell wrapper around the xfs_db(8) metadump command.
SEE ALSO
xfs_repair(8), xfs_mdrestore(8), xfs_freeze(8), xfs_db(8), xfs_copy(8), xfs(5)
BUGS
Email bug reports to xfs@oss.sgi.com.
xfs_metadump(8)