commit 4df0b9903d391b7531e06ca859c46f261335bdc1 · pyrox.dev/nixpkgs

+28

nixos/doc/manual/administration/store-corruption.section.md

···

       1
       1
       +
       # Nix Store Corruption {#sec-nix-store-corruption}

     

       2
       2
       +
       

     

       3
       3
       +
       After a system crash, it's possible for files in the Nix store to become

     

       4
       4
       +
       corrupted. (For instance, the Ext4 file system has the tendency to

     

       5
       5
       +
       replace un-synced files with zero bytes.) NixOS tries hard to prevent

     

       6
       6
       +
       this from happening: it performs a `sync` before switching to a new

     

       7
       7
       +
       configuration, and Nix's database is fully transactional. If corruption

     

       8
       8
       +
       still occurs, you may be able to fix it automatically.

     

       9
       9
       +
       

     

       10
       10
       +
       If the corruption is in a path in the closure of the NixOS system

     

       11
       11
       +
       configuration, you can fix it by doing

     

       12
       12
       +
       

     

       13
       13
       +
       ```ShellSession

     

       14
       14
       +
       # nixos-rebuild switch --repair

     

       15
       15
       +
       ```

     

       16
       16
       +
       

     

       17
       17
       +
       This will cause Nix to check every path in the closure, and if its

     

       18
       18
       +
       cryptographic hash differs from the hash recorded in Nix's database, the

     

       19
       19
       +
       path is rebuilt or redownloaded.

     

       20
       20
       +
       

     

       21
       21
       +
       You can also scan the entire Nix store for corrupt paths:

     

       22
       22
       +
       

     

       23
       23
       +
       ```ShellSession

     

       24
       24
       +
       # nix-store --verify --check-contents --repair

     

       25
       25
       +
       ```

     

       26
       26
       +
       

     

       27
       27
       +
       Any corrupt paths will be redownloaded if they're available in a binary

     

       28
       28
       +
       cache; otherwise, they cannot be repaired.

-36

nixos/doc/manual/administration/store-corruption.xml

···

       1
       1
       -
       <section xmlns="http://docbook.org/ns/docbook"

     

       2
       2
       -
               xmlns:xlink="http://www.w3.org/1999/xlink"

     

       3
       3
       -
               xmlns:xi="http://www.w3.org/2001/XInclude"

     

       4
       4
       -
               version="5.0"

     

       5
       5
       -
               xml:id="sec-nix-store-corruption">

     

       6
       6
       -
        <title>Nix Store Corruption</title>

     

       7
       7
       -
       

     

       8
       8
       -
        <para>

     

       9
       9
       -
         After a system crash, it’s possible for files in the Nix store to become

     

       10
       10
       -
         corrupted. (For instance, the Ext4 file system has the tendency to replace

     

       11
       11
       -
         un-synced files with zero bytes.) NixOS tries hard to prevent this from

     

       12
       12
       -
         happening: it performs a <command>sync</command> before switching to a new

     

       13
       13
       -
         configuration, and Nix’s database is fully transactional. If corruption

     

       14
       14
       -
         still occurs, you may be able to fix it automatically.

     

       15
       15
       -
        </para>

     

       16
       16
       -
       

     

       17
       17
       -
        <para>

     

       18
       18
       -
         If the corruption is in a path in the closure of the NixOS system

     

       19
       19
       -
         configuration, you can fix it by doing

     

       20
       20
       -
       <screen>

     

       21
       21
       -
       <prompt># </prompt>nixos-rebuild switch --repair

     

       22
       22
       -
       </screen>

     

       23
       23
       -
         This will cause Nix to check every path in the closure, and if its

     

       24
       24
       -
         cryptographic hash differs from the hash recorded in Nix’s database, the

     

       25
       25
       -
         path is rebuilt or redownloaded.

     

       26
       26
       -
        </para>

     

       27
       27
       -
       

     

       28
       28
       -
        <para>

     

       29
       29
       -
         You can also scan the entire Nix store for corrupt paths:

     

       30
       30
       -
       <screen>

     

       31
       31
       -
       <prompt># </prompt>nix-store --verify --check-contents --repair

     

       32
       32
       -
       </screen>

     

       33
       33
       -
         Any corrupt paths will be redownloaded if they’re available in a binary

     

       34
       34
       -
         cache; otherwise, they cannot be repaired.

     

       35
       35
       -
        </para>

     

       36
       36
       -
       </section>

+1 -1

nixos/doc/manual/administration/troubleshooting.xml

···

       11
       11
        
        <xi:include href="../from_md/administration/boot-problems.section.xml" />

     

       12
       12
        
        <xi:include href="../from_md/administration/maintenance-mode.section.xml" />

     

       13
       13
        
        <xi:include href="../from_md/administration/rollback.section.xml" />

     

       14
       14
       -
        <xi:include href="store-corruption.xml" />

     

       14
       14
       +
        <xi:include href="../from_md/administration/store-corruption.section.xml" />

     

       15
       15
        
        <xi:include href="network-problems.xml" />

     

       16
       16
        
       </chapter>

+34

nixos/doc/manual/from_md/administration/store-corruption.section.xml

···

       1
       1
       +
       <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-nix-store-corruption">

     

       2
       2
       +
         <title>Nix Store Corruption</title>

     

       3
       3
       +
         <para>

     

       4
       4
       +
           After a system crash, it’s possible for files in the Nix store to

     

       5
       5
       +
           become corrupted. (For instance, the Ext4 file system has the

     

       6
       6
       +
           tendency to replace un-synced files with zero bytes.) NixOS tries

     

       7
       7
       +
           hard to prevent this from happening: it performs a

     

       8
       8
       +
           <literal>sync</literal> before switching to a new configuration, and

     

       9
       9
       +
           Nix’s database is fully transactional. If corruption still occurs,

     

       10
       10
       +
           you may be able to fix it automatically.

     

       11
       11
       +
         </para>

     

       12
       12
       +
         <para>

     

       13
       13
       +
           If the corruption is in a path in the closure of the NixOS system

     

       14
       14
       +
           configuration, you can fix it by doing

     

       15
       15
       +
         </para>

     

       16
       16
       +
         <programlisting>

     

       17
       17
       +
       # nixos-rebuild switch --repair

     

       18
       18
       +
       </programlisting>

     

       19
       19
       +
         <para>

     

       20
       20
       +
           This will cause Nix to check every path in the closure, and if its

     

       21
       21
       +
           cryptographic hash differs from the hash recorded in Nix’s database,

     

       22
       22
       +
           the path is rebuilt or redownloaded.

     

       23
       23
       +
         </para>

     

       24
       24
       +
         <para>

     

       25
       25
       +
           You can also scan the entire Nix store for corrupt paths:

     

       26
       26
       +
         </para>

     

       27
       27
       +
         <programlisting>

     

       28
       28
       +
       # nix-store --verify --check-contents --repair

     

       29
       29
       +
       </programlisting>

     

       30
       30
       +
         <para>

     

       31
       31
       +
           Any corrupt paths will be redownloaded if they’re available in a

     

       32
       32
       +
           binary cache; otherwise, they cannot be repaired.

     

       33
       33
       +
         </para>

     

       34
       34
       +
       </section>