Fsck - Revision history

Pbug: where is my eyes there was something wrong with dumpfs -m

2008-06-05T14:33:37Z

where is my eyes there was something wrong with dumpfs -m

@@ Line 7: / Line 7: @@
 If you have a journalling filesystem you don't need to fsck.
-If the superblock is corrupted fsck won't work without the -b option which you have to state one of several backup superblocks.  Knowledge of the backup superblock is only known if the administrator keeps a record of where the backup block are (mostly from newfs time).  There is a way to use newfs to display the superblocks and not write into the filesystem (use with the dumpfs -m command in conjunction).
+If the superblock is corrupted fsck won't work without the -b option which you have to state one of several backup superblocks.  Knowledge of the backup superblock is only known if the administrator keeps a record of where the backup block are (mostly from newfs time).  There is a way to use newfs to display the superblocks and not write into the filesystem.
   # fsck -y -b 32
@@ Line 15: / Line 15: @@
   [[fdisk]] of disk
   [[disklabel]] of disk
-  [[newfs]] / newfs -N (dumpfs -m)
+  [[newfs]] / newfs -N
 If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted.  Make sure you understand what these things do so when you gain this data that you don't do any damage (newfs with -N should never write to disk and give you superblocks).

Pbug: newfs -N example

2008-06-05T13:42:19Z

newfs -N example

@@ Line 8: / Line 8: @@
 If the superblock is corrupted fsck won't work without the -b option which you have to state one of several backup superblocks.  Knowledge of the backup superblock is only known if the administrator keeps a record of where the backup block are (mostly from newfs time).  There is a way to use newfs to display the superblocks and not write into the filesystem (use with the dumpfs -m command in conjunction).
   # fsck -y -b 32
@@ Line 18: / Line 18: @@
 If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted.  Make sure you understand what these things do so when you gain this data that you don't do any damage (newfs with -N should never write to disk and give you superblocks).

Pbug at 13:34, 5 June 2008

2008-06-05T13:34:35Z

← Older revision		Revision as of 06:34, 5 June 2008
Line 13:		Line 13:
	It's good to have the following things stored offsite in order to repair a filesystem:		It's good to have the following things stored offsite in order to repair a filesystem:

	fdisk of disk		[[fdisk]] of disk
	disklabel of disk		[[disklabel]] of disk
	newfs / newfs -N (dumpfs -m)		[[newfs]] / newfs -N (dumpfs -m)

	If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted. Make sure you understand what these things do so when you gain this data that you don't do any damage (newfs with -N should never write to disk and give you superblocks).		If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted. Make sure you understand what these things do so when you gain this data that you don't do any damage (newfs with -N should never write to disk and give you superblocks).

Pbug at 13:32, 5 June 2008

2008-06-05T13:32:41Z

← Older revision		Revision as of 06:32, 5 June 2008
Line 17:		Line 17:
	newfs / newfs -N (dumpfs -m)		newfs / newfs -N (dumpfs -m)

	If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted.		If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted. Make sure you understand what these things do so when you gain this data that you don't do any damage (newfs with -N should never write to disk and give you superblocks).

Pbug at 13:29, 5 June 2008

2008-06-05T13:29:23Z

← Older revision		Revision as of 06:29, 5 June 2008
Line 6:		Line 6:

	If you have a journalling filesystem you don't need to fsck.		If you have a journalling filesystem you don't need to fsck.

			If the superblock is corrupted fsck won't work without the -b option which you have to state one of several backup superblocks. Knowledge of the backup superblock is only known if the administrator keeps a record of where the backup block are (mostly from newfs time). There is a way to use newfs to display the superblocks and not write into the filesystem (use with the dumpfs -m command in conjunction).

			# fsck -y -b 32

			It's good to have the following things stored offsite in order to repair a filesystem:

			fdisk of disk
			disklabel of disk
			newfs / newfs -N (dumpfs -m)

			If you have this information on a floppy next to the backup tapes you greatly increase your chances to repair your data if it's corrupted.

Pbug: comma

2008-06-05T13:22:59Z

comma

← Older revision		Revision as of 06:22, 5 June 2008
Line 1:		Line 1:
	The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.		The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt, the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.

	If you shut down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts:		If you shut down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts:

Frankk at 22:21, 20 November 2005

2005-11-20T22:21:48Z

← Older revision		Revision as of 15:21, 20 November 2005
Line 5:		Line 5:
	# fsck -y		# fsck -y

	If you have a ~~journaled~~ filesystem you don't need to fsck.		If you have a journalling filesystem you don't need to fsck.

Frankk at 22:21, 20 November 2005

2005-11-20T22:21:32Z

← Older revision		Revision as of 15:21, 20 November 2005
Line 1:		Line 1:
	The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.		The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.

	If you ~~show~~ down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts		If you shut down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts:

	# fsck -y		# fsck -y

			If you have a journaled filesystem you don't need to fsck.

Frankk at 15:48, 2 November 2005

2005-11-02T15:48:23Z

← Older revision		Revision as of 08:48, 2 November 2005
Line 1:		Line 1:
	The '''filesystem consistency check and interactive repair''' program is needed on [[~~ffs~~]] ~~style~~ [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.		The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.

	If you show down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts		If you show down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts

	# fsck -y		# fsck -y

Pbug at 11:49, 2 November 2005

2005-11-02T11:49:41Z

← Older revision		Revision as of 04:49, 2 November 2005
Line 1:		Line 1:
	The '''filesystem consistency check and interactive repair''' program. When a filesystem is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.		The '''filesystem consistency check and interactive repair''' program is needed on [[ffs]] style [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent.

	If you show down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts		If you show down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts

	# fsck -y		# fsck -y