Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Apress - Books for Professionals by Professionals

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 65 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

xfs_check



SYNOPSIS

       xfs_check [ -i ino ] ... [ -b bno ] ... [ -s ] [ -v ] xfs_special

       xfs_check -f [ -i ino ] ... [ -b bno ] ... [ -s ] [ -v ] file


DESCRIPTION

       xfs_check  checks whether an XFS filesystem is consistent.
       It is normally run only when there is  reason  to  believe
       that  the  filesystem  has  a  consistency  problem.   The
       filesystem to be checked is specified by  the  xfs_special
       argument,  which  should  be the disk or volume device for
       the filesystem.  Filesystems stored in files can  also  be
       checked,  using  the  -f flag.  The filesystem should nor­
       mally be unmounted or read-only during  the  execution  of
       xfs_check.  Otherwise, spurious problems are reported.

       The options to xfs_check are:

       -f       Specifies  that  the special device is actually a
                file (see the mkfs.xfs  -d  file  option).   This
                might happen if an image copy of a filesystem has
                been made into an ordinary file.

       -s       Specifies that  only  serious  errors  should  be
                reported.   Serious errors are those that make it
                impossible to find major data structures  in  the
                filesystem.   This option can be used to cut down
                the amount of output  when  there  is  a  serious
                problem,  when the output might make it difficult
                to see what the real problem is.

       -v       Specifies verbose output; it is  impossibly  long
                for  a  reasonably-sized filesystem.  This option
                is intended for internal use only.

       -i ino   Specifies verbose behavior for a specific  inode.
                For  instance,  it  can be used to locate all the
                blocks associated with a given inode.

       -b bno   Specifies  verbose  behavior   for   a   specific
                filesystem  block.   For instance, it can be used
                to determine what a specific block is  used  for.
                The block number is a "file system block number".
                Conversion between disk addresses (i.e. addresses
                reported  by xfs_bmap) and file system blocks may
                be accomplished using xfs_db's convert command.

       Any non-verbose  output  from  xfs_check  means  that  the
       filesystem  has  an  inconsistency.  The filesystem can be
       repaired using either xfs_repair(8) to fix the  filesystem
       in  place,  or by using xfsdump(8) and mkfs.xfs(8) to dump
       the filesystem, make a new  filesystem,  then  use  xfsre­
       xfs_check might run out of memory.  In this case the  mes­
       sage out of memory is printed.

       The following is a description of the most likely problems
       and the associated messages.  Most of the diagnostics pro­
       duced  are  only  meaningful  with an understanding of the
       structure of the filesystem.

       agf_freeblks n, counted m in ag a
              The freeblocks count in the allocation group header
              for  allocation group a doesn't match the number of
              blocks counted free.

       agf_longest n, counted m in ag a
              The longest free extent  in  the  allocation  group
              header  for  allocation  group  a doesn't match the
              longest free extent found in the allocation  group.

       agi_count n, counted m in ag a
              The  allocated  inode count in the allocation group
              header for allocation group  a  doesn't  match  the
              number of inodes counted in the allocation group.

       agi_freecount n, counted m in ag a
              The free inode count in the allocation group header
              for allocation group a doesn't match the number  of
              inodes counted free in the allocation group.

       block a/b expected inum 0 got i
              The block number is specified as a pair (allocation
              group number, block in the allocation group).   The
              block is used multiple times (shared), between mul­
              tiple inodes.  This message usually follows a  mes­
              sage of the next type.

       block a/b expected type unknown got y
              The block is used multiple times (shared).

       block a/b type unknown not expected
              The  block  is unaccounted for (not in the freelist
              and not in use).

       link count mismatch for inode nnn  (name  xxx),  nlink  m,
       counted n
              The inode has a bad link count  (number  of  refer­
              ences in directories).

       rtblock b expected inum 0 got i
              The  block is used multiple times (shared), between
              multiple inodes.  This message  usually  follows  a
              message of the next type.

              The  number  of  free real-time extents recorded in
              the superblock doesn't  match  the  number  counted
              free in the filesystem.

       sb_icount n, counted m
              The  number  of  allocated  inodes  recorded in the
              superblock doesn't match the  number  allocated  in
              the filesystem.

       sb_ifree n, counted m
              The   number   of   free  inodes  recorded  in  the
              superblock doesn't match the  number  free  in  the
              filesystem.


SEE ALSO

       mkfs.xfs(8),   xfsdump(8),  xfsrestore(8),  xfs_ncheck(8),
       xfs_repair(8), xfs(5).

                                                     xfs_check(8)
  

There are several different ways to navigate the tutorial.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.16 Seconds