ChangeLog, e2fsck.8.in:

  e2fsck.8.in: Add explanation that you can use mke2fs -n -b blocksize
  	to printout alternate superblock locations.

diff --git a/e2fsck/ChangeLog b/e2fsck/ChangeLog
index e14d9483b764ebbe49c1cb08116082dfb730af86..946de7699a635085f95b7c8f2afd6e0cc70a8341 100644 (file)
--- a/e2fsck/ChangeLog
+++ b/e2fsck/ChangeLog
@@ -1,3 +1,8 @@
+2001-05-01  Theodore Tso  <tytso@valinux.com>
+
+       * e2fsck.8.in: Add explanation that you can use mke2fs -n -b
+               blocksize to printout alternate superblock locations.
+
 2001-04-26  Theodore Tso  <tytso@valinux.com>
 
        * unix.c (check_if_skip): If the max_mount_count is zero, treat it

diff --git a/e2fsck/e2fsck.8.in b/e2fsck/e2fsck.8.in
index c76ff036d09e4ecd751aa2a0da92a264af0ecc3a..378c9080a338b7713485af07356469c701b275a3 100644 (file)
--- a/e2fsck/e2fsck.8.in
+++ b/e2fsck/e2fsck.8.in
@@ -54,8 +54,20 @@ This option is normally used when the primary superblock has been
 corrupted.  The location of the backup superblock is dependent on the
 filesystem's blocksize.  For filesystems with 1k blocksizes, a backup
 superblock can be found at block 8193; for filesystems with 2k
-blocksizes, at block 16384; and for 4k blocksizes, at block 32768.  If
-an alternative superblock is specified and  
+blocksizes, at block 16384; and for 4k blocksizes, at block 32768.  
+.IP
+Additional backup superblocks can be determined by using the 
+.B mke2fs 
+program using the 
+.B \-n
+option to print out where the superblocks were created.   The 
+.B \-b 
+option to 
+.BR mke2fs ,
+which specifies blocksize of the filesystem must be specified in order
+for the superblock locations that are printed out to be accurate.
+.IP
+If an alternative superblock is specified and  
 the filesystem is not opened read-only, e2fsck will make sure that the
 primary superblock is updated appropriately upon completion of the 
 filesystem check.