diff options
Diffstat (limited to 'sag-0.6.1-www/Invisible/sag-0.6/node48.html')
| -rw-r--r-- | sag-0.6.1-www/Invisible/sag-0.6/node48.html | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/sag-0.6.1-www/Invisible/sag-0.6/node48.html b/sag-0.6.1-www/Invisible/sag-0.6/node48.html new file mode 100644 index 0000000..bb507ee --- /dev/null +++ b/sag-0.6.1-www/Invisible/sag-0.6/node48.html @@ -0,0 +1,52 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> +<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds --> +<HTML> +<HEAD> +<TITLE>Checking for disk errors with badblocks</TITLE> +<META NAME="description" CONTENT="Checking for disk errors with badblocks"> +<META NAME="keywords" CONTENT="sag"> +<META NAME="resource-type" CONTENT="document"> +<META NAME="distribution" CONTENT="global"> +<LINK REL=STYLESHEET HREF="sag.css"> +</HEAD> +<BODY LANG="EN" > + <A NAME="tex2html921" HREF="node49.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html919" HREF="node41.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html913" HREF="node47.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html923" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html924" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR> +<B> Next:</B> <A NAME="tex2html922" HREF="node49.html">Fighting fragmentation</A> +<B>Up:</B> <A NAME="tex2html920" HREF="node41.html">Filesystems</A> +<B> Previous:</B> <A NAME="tex2html914" HREF="node47.html">Checking filesystem integrity with </A> +<BR> <P> +<A NAME="1715"> </A><H2><A NAME="SECTION00587000000000000000">Checking for disk errors with <tt>badblocks</tt></A></H2> +<P> + It can be a good idea to periodically check for bad blocks. + This is done with the <tt>badblocks</tt><A NAME="1717"> </A> command. It outputs + a list of the numbers of all bad blocks it can find. This list + can be fed to <tt>fsck</tt><A NAME="1719"> </A> to be recorded + in the filesystem data structures so that the operating system + won't try to use the bad blocks for storing data. + The following example will show how this could be done. + <BLOCKQUOTE> <TT> +<code>$</code> <I>badblocks /dev/fd0H1440 1440 > bad-blocks </I> <BR> +<code>$</code> <I>fsck -t ext2 -l bad-blocks /dev/fd0H1440</I> <BR> +<code>Parallelizing fsck version 0.5a (5-Apr-94)</code> <BR> +<code>e2fsck 0.5a, 5-Apr-94 for EXT2 FS 0.5, 94/03/10</code> <BR> +<code>Pass 1: Checking inodes, blocks, and sizes</code> <BR> +<code>Pass 2: Checking directory structure</code> <BR> +<code>Pass 3: Checking directory connectivity</code> <BR> +<code>Pass 4: Check reference counts.</code> <BR> +<code>Pass 5: Checking group summary information.</code> <BR> +<code> </code> <BR> +<code>/dev/fd0H1440: ***** FILE SYSTEM WAS MODIFIED *****</code> <BR> +<code>/dev/fd0H1440: 11/360 files, 63/1440 blocks</code> <BR> +<code>$ </code> + </TT></BLOCKQUOTE> + If badblocks reports a block that was already used, <tt>e2fsck</tt><A NAME="1721"> </A> + will try to move the block to another place. If the block was really + bad, not just marginal, the contents of the file may be corrupted. +<P> +<BR> <HR> +<P><ADDRESS> +<I>Lars Wirzenius <BR> +Sat Nov 15 02:32:11 EET 1997</I> +</ADDRESS> +</BODY> +</HTML> |