xfsprogs - en to unknown language translation catalogue (55 entries)

en: 
     Repairs a piece of XFS filesystem metadata.  The first argument is the type
     of metadata to examine.  Allocation group metadata types take one AG number
     as the second parameter.  Inode metadata types act on the currently open file
     or (optionally) take an inode number and generation number to act upon as
     the second and third parameters.
    
     Example:
     'repair inobt 3' - repairs the inode btree in AG 3.
     'repair bmapbtd 128 13525' - repairs the extent map of inode 128 gen 13525.
    
     Known metadata repairs types are:
target: 
     Repairs a piece of XFS filesystem metadata.  The first argument is the type
     of metadata to examine.  Allocation group metadata types take one AG number
     as the second parameter.  Inode metadata types act on the currently open file
     or (optionally) take an inode number and generation number to act upon as
     the second and third parameters.
    
     Example:
     >>repair inobt 3<< - repairs the inode btree in AG 3.
     >>repair bmapbtd 128 13525<< - repairs the extent map of inode 128 gen 13525.
    
     Known metadata repairs types are:

en: 
     Shuts down the filesystem and prevents any further IO from occurring.
    
     By default, shutdown will not flush completed transactions to disk
     before shutting the filesystem down, simulating a disk failure or crash.
     With -f, the log will be flushed to disk, matching XFS behavior when
     metadata corruption is encountered.
    
     -f -- Flush completed transactions to disk before shut down.
target: 
     Shuts down the filesystem and prevents any further IO from occurring.
    
     By default, shutdown will not flush completed transactions to disk
     before shutting the filesystem down, simulating a disk failure or crash.
     With -f, the log will be flushed to disk, matching XFS behaviour when
     metadata corruption is encountered.
    
     -f -- Flush completed transactions to disk before shut down.

en: 
     The 'fuzz' command fuzzes fields in any on-disk data structure.  For
     block fuzzing, see the 'blocktrash' or 'write' commands.
     Examples:
      Struct mode: 'fuzz core.uid zeroes'    - set an inode uid field to 0.
                   'fuzz crc ones'           - set a crc filed to all ones.
                   'fuzz bno[11] firstbit'   - set the high bit of a block array.
                   'fuzz keys[5].startblock add'    - increase a btree key value.
                   'fuzz uuid random'        - randomize the superblock uuid.
    
     Type 'fuzz' by itself for a list of specific commands.
    
     Specifying the -c option will allow writes of invalid (corrupt) data with
     an invalid CRC. Specifying the -d option will allow writes of invalid data,
     but still recalculate the CRC so we are forced to check and detect the
     invalid data appropriately.
target: 
     The 'fuzz' command fuzzes fields in any on-disk data structure.  For
     block fuzzing, see the 'blocktrash' or 'write' commands.
     Examples:
      Struct mode: 'fuzz core.uid zeroes'    - set an inode uid field to 0.
                   'fuzz crc ones'           - set a crc filed to all ones.
                   'fuzz bno[11] firstbit'   - set the high bit of a block array.
                   'fuzz keys[5].startblock add'    - increase a btree key value.
                   'fuzz uuid random'        - randomise the superblock uuid.
    
     Type 'fuzz' by itself for a list of specific commands.
    
     Specifying the -c option will allow writes of invalid (corrupt) data with
     an invalid CRC. Specifying the -d option will allow writes of invalid data,
     but still recalculate the CRC so we are forced to check and detect the
     invalid data appropriately.

en: 
     The 'logres' command prints information about all log reservation types.
     This includes the reservation space, the intended transaction roll count,
     and the reservation flags, if any.
target: 
     The >>logres<< command prints information about all log reservation types.
     This includes the reservation space, the intended transaction roll count,
     and the reservation flags, if any.

en: 
     Update file atime and mtime of the current file with nansecond precision.
    
     Usage: utimes atime_sec atime_nsec mtime_sec mtime_nsec.
     *_sec: Seconds elapsed since 1970-01-01 00:00:00 UTC.
     *_nsec: Nanoseconds since the corresponding *_sec.
target: 
     Update file atime and mtime of the current file with nanosecond precision.
    
     Usage: utimes atime_sec atime_nsec mtime_sec mtime_nsec.
     *_sec: Seconds elapsed since 1970-01-01 00:00:00 UTC.
     *_nsec: Nanoseconds since the corresponding *_sec.

en: 
     advise the page cache about access patterns expected for a mapping
    
     Modifies page cache behavior when operating on the current mapping.
     The range arguments are required by some advise commands ([*] below).
     With no arguments, the POSIX_MADV_NORMAL advice is implied.
     -d -- don't need these pages (POSIX_MADV_DONTNEED) [*]
     -r -- expect random page references (POSIX_MADV_RANDOM)
     -s -- expect sequential page references (POSIX_MADV_SEQUENTIAL)
     -w -- will need these pages (POSIX_MADV_WILLNEED) [*]
     Notes:
       NORMAL sets the default readahead setting on the file.
       RANDOM sets the readahead setting on the file to zero.
       SEQUENTIAL sets double the default readahead setting on the file.
       WILLNEED forces the maximum readahead.
target: 
     advise the page cache about access patterns expected for a mapping
    
     Modifies page cache behaviour when operating on the current mapping.
     The range arguments are required by some advise commands ([*] below).
     With no arguments, the POSIX_MADV_NORMAL advice is implied.
     -d -- don't need these pages (POSIX_MADV_DONTNEED) [*]
     -r -- expect random page references (POSIX_MADV_RANDOM)
     -s -- expect sequential page references (POSIX_MADV_SEQUENTIAL)
     -w -- will need these pages (POSIX_MADV_WILLNEED) [*]
     Notes:
       NORMAL sets the default readahead setting on the file.
       RANDOM sets the readahead setting on the file to zero.
       SEQUENTIAL sets double the default readahead setting on the file.
       WILLNEED forces the maximum readahead.

en: 
     list the current file's parents and their filenames
    
     -c -- check the current file's file system for parent consistency
     -p -- list the current file's parents and their full paths
     -v -- verbose mode
target: 
     list the current file's parents and their filenames
    
     -c -- check the current file's filesystem for parent consistency
     -p -- list the current file's parents and their full paths
     -v -- verbose mode

en: 
     opens a new file in the requested mode
    
     Example:
     'open -cd /tmp/data' - creates/opens data file read-write for direct IO
    
     Opens a file for subsequent use by all of the other xfs_io commands.
     With no arguments, open uses the stat command to show the current file.
     -a -- open with the O_APPEND flag (append-only mode)
     -d -- open with O_DIRECT (non-buffered IO, note alignment constraints)
     -f -- open with O_CREAT (create the file if it doesn't exist)
     -m -- permissions to use in case a new file is created (default 0600)
     -n -- open with O_NONBLOCK
     -r -- open with O_RDONLY, the default is O_RDWR
     -s -- open with O_SYNC
     -t -- open with O_TRUNC (truncate the file to zero length if it exists)
     -R -- mark the file as a realtime XFS file immediately after opening it
     -T -- open with O_TMPFILE (create a file not visible in the namespace)
     -P -- open with O_PATH (create an fd that is merely a location reference)
     -L -- open with O_NOFOLLOW (don't follow symlink)
     Note1: usually read/write direct IO requests must be blocksize aligned;
            some kernels, however, allow sectorsize alignment for direct IO.
     Note2: the bmap for non-regular files can be obtained provided the file
            was opened correctly (in particular, must be opened read-only).
target: 
     opens a new file in the requested mode
    
     Example:
     >>open -cd /tmp/data<< - creates/opens data file read-write for direct IO
    
     Opens a file for subsequent use by all of the other xfs_io commands.
     With no arguments, open uses the stat command to show the current file.
     -a -- open with the O_APPEND flag (append-only mode)
     -d -- open with O_DIRECT (non-buffered IO, note alignment constraints)
     -f -- open with O_CREAT (create the file if it doesn't exist)
     -m -- permissions to use in case a new file is created (default 0600)
     -n -- open with O_NONBLOCK
     -r -- open with O_RDONLY, the default is O_RDWR
     -s -- open with O_SYNC
     -t -- open with O_TRUNC (truncate the file to zero length if it exists)
     -R -- mark the file as a realtime XFS file immediately after opening it
     -T -- open with O_TMPFILE (create a file not visible in the namespace)
     -P -- open with O_PATH (create an fd that is merely a location reference)
     -L -- open with O_NOFOLLOW (don't follow symlink)
     Note1: usually read/write direct IO requests must be blocksize aligned;
            some kernels, however, allow sectorsize alignment for direct IO.
     Note2: the bmap for non-regular files can be obtained provided the file
            was opened correctly (in particular, must be opened read-only).

en: 
     set allocation group free block list
    
     Example:
    
     agf 2 - move location to AGF in 2nd filesystem allocation group
    
     Located in the second sector of each allocation group, the AGF
     contains the root of two different freespace btrees:
     The 'cnt' btree keeps track freespace indexed on section size.
     The 'bno' btree tracks sections of freespace indexed on block number.
target: 
     set allocation group free block list
    
     Example:
    
     agf 2 - move location to AGF in 2nd file-system allocation group
    
     Located in the second sector of each allocation group, the AGF
     contains the root of two different freespace btrees:
     The 'cnt' btree keeps track freespace indexed on section size.
     The 'bno' btree tracks sections of freespace indexed on block number.

en: 
    fatal error -- couldn't initialize XFS library
target: 
    fatal error -- couldn't initialise XFS library

en:   -e behavior  What to do if errors are found.
target:   -e behaviour  What to do if errors are found.

en: %s %s filesystem failed to initialize
    %s: Aborting.
target: %s %s filesystem failed to initialise
    %s: Aborting.

en: %s: %s filesystem failed to initialize
    %s: Aborting.
target: %s: %s filesystem failed to initialise
    %s: Aborting.

en: %s: couldn't initialize Unicode library.
target: %s: couldn't initialise Unicode library.

en: %s: couldn't initialize XFS library
    %s: Aborting.
target: %s: couldn't initialise XFS library
    %s: Aborting.

en: %s: filesystem failed to initialize
target: %s: filesystem failed to initialise

en: %s: optimizations made: %llu.
target: %s: optimisations made: %llu.

en: %s: repairs made: %llu; optimizations made: %llu.
target: %s: repairs made: %llu; optimisations made: %llu.

en: %s: unrecognized btree header type.
target: %s: unrecognised btree header type.

en: %s: unrecognized raw btree geometry.
target: %s: unrecognised raw btree geometry.

en: Attempting optimization.
target: Attempting optimisation.

en: Couldn't initialize global thread mask
target: Couldn't initialise global thread mask

en: Error initializing btree buf 1
target: Error initialising btree buf 1

en: Error initializing the realtime space
target: Error initialising the realtime space

en: Error initializing wbuf 0
target: Error initialising wbuf 0

en: File system metadata writeout failed, err=%d.  Re-run xfs_repair.
target: Filesystem metadata writeout failed, err=%d.  Re-run xfs_repair.

en: Initialization of the realtime space failed
target: Initialisation of the realtime space failed

en: Metadata did not need repair or optimization.
target: Metadata did not need repair or optimisation.

en: Optimization is possible.
target: Optimisation is possible.

en: Optimization possible.
target: Optimisation possible.

en: Optimization successful.
target: Optimisation successful.

en: Optimizations of %s are possible.
target: Optimisations of %s are possible.

en: Unicode name "%s" in %s could be confused with '%s' due to invisible characters.
target: Unicode name "%s" in %s could be confused with >>%s<< due to invisible characters.

en: Unknown error behavior "%s".
target: Unknown error behaviour "%s".

en: Unrecognized AG number: %s
target: Unrecognised AG number: %s

en: Unrecognized metadata or type mismatch
target: Unrecognised metadata or type mismatch

en: Value not recognized as number.
target: Value not recognised as number.

en: Warning:  group quota information was cleared.
    Group quotas can not be enforced until limit information is recreated.
target: Warning:  group quota information was cleared.
    Group quotas cannot be enforced until limit information is recreated.

en: Warning:  project quota information was cleared.
    Project quotas can not be enforced until limit information is recreated.
target: Warning:  project quota information was cleared.
    Project quotas cannot be enforced until limit information is recreated.

en: Warning:  user quota information was cleared.
    User quotas can not be enforced until limit information is recreated.
target: Warning:  user quota information was cleared.
    User quotas cannot be enforced until limit information is recreated.

en: couldn't initialize XFS library
target: couldn't initialise XFS library

en: failed to initialize prefetch cond var
target: failed to initialise prefetch cond var

en: failed to initialize prefetch mutex
target: failed to initialise prefetch mutex

en: initialize realtime bitmap
target: initialise realtime bitmap

en: initializing AG free space list
target: initialising AG free space list

en: journalling log
target: journaling log

en: no rw xfs file systems in mtab: %s
target: no rw xfs filesystems in mtab: %s

en: randomized
target: randomised

en: reinitializing realtime bitmap inode
target: reinitialising realtime bitmap inode

en: reinitializing realtime summary inode
target: reinitialising realtime summary inode

en: reinitializing root directory
target: reinitialising root directory

en: summarize filesystem ownership
target: summarise filesystem ownership

en: would reinitialize realtime bitmap inode
target: would reinitialise realtime bitmap inode

en: would reinitialize realtime summary inode
target: would reinitialise realtime summary inode

en: would reinitialize root directory
target: would reinitialise root directory
