Editing Talk:1678: Recent Searches

Jump to: navigation, search
Ambox notice.png Please sign your posts with ~~~~

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 69: Line 69:
 
::As long as you are not trying to run the fsck on ROOT filesystem (or /home, or anything other currently mounted), it doesn't matter if it's chrome extension. But it's true that usually fsck is run as part of system boot, when no filesystem is mounted in read/write mode, and it is not possible to run Chrome in such situation. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 03:57, 16 May 2016 (UTC)
 
::As long as you are not trying to run the fsck on ROOT filesystem (or /home, or anything other currently mounted), it doesn't matter if it's chrome extension. But it's true that usually fsck is run as part of system boot, when no filesystem is mounted in read/write mode, and it is not possible to run Chrome in such situation. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 03:57, 16 May 2016 (UTC)
  
βˆ’
: [Extended explanation] Information about files often occur in multiple places on the disk. This redundancy increase the chance of repairing a corrupt file system. Fsck will read data from the disk, and if it finds inconsistencies, write new corrected data back. When a file system is mounted, a file system driver will read and write data of the disk in normal operation. If the two processes are simultaneous and unaware of each other, they may be confused and even create inconsistencies that wasn't there to begin with. E.g. original research: A file system driver may have cached data in working memory. If fsck updates that data on disk, the cache will be out of sync. The file system driver may be confused by this, or, if it writes back the cache to the disk, the fsck fix will be undone, and possibly a new different inconsistency would be created. Or, while fsck is comparing different parts of the file system, it will read one block at one point in time and another block at another point in time. At a time in between, normal operation may have created, changed or removed a file. Fsck then may think it has found an inconsistency (that does not exists) and try to fix it, possibly creating an inconsistency. Therefor, the fsck command will detect if a file system is mounted and issue a really scary warning against proceeding. /David A [[Special:Contributions/141.101.80.33|141.101.80.33]] 21:22, 24 September 2016 (UTC)
+
: [Extended explanation] Information about files often occur in multiple places on the disk. This redundancy increase the chance of repairing a corrupt file system. Fsck will read data from the disk, and if it finds inconsistencies, write new corrected data back. When a file system is mounted, a file system driver will read and write data of the disk in normal operation. If the two processes are simultaneous and unaware of each other, they may be confused and even create inconsistencies that wasn't there to begin with. E.g. {{original research}}: A file system driver may have cached data in working memory. If fsck updates that data on disk, the cache will be out of sync. The file system driver may be confused by this, or, if it writes back the cache to the disk, the fsck fix will be undone, and possibly a new different inconsistency would be created. Or, while fsck is comparing different parts of the file system, it will read one block at one point in time and another block at another point in time. At a time in between, normal operation may have created, changed or removed a file. Fsck then may think it has found an inconsistency (that does not exists) and try to fix it, possibly creating an inconsistency. Therefor, the fsck command will detect if a file system is mounted and issue a really scary warning against proceeding. /David A [[Special:Contributions/141.101.80.33|141.101.80.33]] 21:22, 24 September 2016 (UTC)
  
 
;Predictable touchpad
 
;Predictable touchpad

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)

Template used on this page: