The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: answer/screen
English
<prompt>#</prompt> <userinput>gjournal load</userinput>

GEOM_JOURNAL: Journal 2948326772: ad0s1g contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1h contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1d contains data.
GEOM_JOURNAL: Journal ad0s1d clean.
GEOM_JOURNAL: Journal 2948326772: ad0s1f contains data.
GEOM_JOURNAL: Journal ad0s1f clean.

<prompt>#</prompt> <userinput>mount -a</userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<emphasis>(boot continues)</emphasis>
495/4950 · 495
Context English Portuguese (Brazil) State
You can then create a file system on your new partition, and enable journaling using the <option>-J</option> option: Você pode criar um sistema de arquivos em sua nova partição e ativar o journaling usando a opção <option> -J </option>:
<prompt>#</prompt> <userinput>newfs -J /dev/ad1s1d.journal</userinput> <prompt>#</prompt> <userinput>newfs -J /dev/ad1s1d.journal</userinput>
Building Journaling into Your Custom Kernel Adicionando suporte ao journaling no seu kernel personalizado
If you do not wish to load <literal>geom_journal</literal> as a module, you can build its functions right into your kernel. Edit your custom kernel configuration file, and make sure it includes these two lines: Se você não deseja carregar o <literal>geom_journal</literal> como um módulo, você pode construir suas funções diretamente em seu kernel. Edite seu arquivo de configuração do kernel personalizado e verifique se ele inclui estas duas linhas:
options UFS_GJOURNAL # Note: This is already in GENERIC

options GEOM_JOURNAL # You will have to add this one 		options UFS_GJOURNAL # Note: This is already in GENERIC

options GEOM_JOURNAL # You will have to add this one
Rebuild and reinstall your kernel following the relevant <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html">instructions in the FreeBSD Handbook.</link> Recompile e reinstale seu kernel seguindo as instruções <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html"> relevantes no Handbook do FreeBSD.</link>
Do not forget to remove the relevant <quote>load</quote> entry from <filename>/boot/loader.conf</filename> if you have previously used it. Não se esqueça de remover a entrada relevante <quote>load</quote> do <filename>/boot/loader.conf</filename> se você a usou anteriormente.
Troubleshooting Journaling Solução de problemas com journaling
The following section covers frequently asked questions regarding problems related to journaling. A seção a seguir aborda as perguntas mais frequentes relacionadas a problemas relacionados ao journaling.
I am getting kernel panics during periods of high disk activity. How is this related to journaling? Estou recebendo um kernel panic durante períodos de alta atividade de disco. Como isso está relacionado ao journaling?
The journal probably fills up before it has a chance to get committed (flushed) to disk. Keep in mind the size of the journal depends on the usage load, and not the size of the data provider. If your disk activity is high, you need a larger partition for the journal. See the note in the <link linkend="understanding-journaling">Understanding Journaling</link> section. O journal provavelmente se enche antes que ele tenha a chance de ser enviado (descarregado) para o disco. Lembre-se de que o tamanho do journal depende da carga de uso e não do tamanho do provedor de dados. Se a atividade do disco for alta, você precisará de uma partição maior para o journal. Veja a nota na seção <link linkend="understanding-journaling"> Noções básicas sobre journaling</link>.
I made some mistake during configuration, and I cannot boot normally now. Can this be fixed some way? Eu cometi algum erro durante a configuração e não consigo inicializar normalmente agora. Isso pode ser resolvido de alguma forma?
You either forgot (or misspelled) the entry in <filename>/boot/loader.conf</filename>, or there are errors in your <filename>/etc/fstab</filename> file. These are usually easy to fix. Press <keycap>Enter</keycap> to get to the default single user shell. Then locate the root of the problem: Você esqueceu (ou escreveu incorretamente) a entrada em <filename>/boot/loader.conf</filename>, ou existem erros no seu arquivo <filename>/etc/fstab</filename>. Estes erros geralmente são fáceis de corrigir. Pressione <keycap>Enter</keycap> para acessar o shell padrão do modo single user. Em seguida, localize a raiz do problema:
<prompt>#</prompt> <userinput>cat /boot/loader.conf</userinput> <prompt>#</prompt> <userinput>cat /boot/loader.conf</userinput>
If the <literal>geom_journal_load</literal> entry is missing or misspelled, the journaled devices are never created. Load the module manually, mount all partitions, and continue with multi-user boot: Se a entrada <literal>geom_journal_load</literal> estiver ausente ou incorreta, os dispositivos registrados nunca serão criados. Carregue o módulo manualmente, monte todas as partições e continue com a inicialização do modo multi usuário:
<prompt>#</prompt> <userinput>gjournal load</userinput>

GEOM_JOURNAL: Journal 2948326772: ad0s1g contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1h contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1d contains data.
GEOM_JOURNAL: Journal ad0s1d clean.
GEOM_JOURNAL: Journal 2948326772: ad0s1f contains data.
GEOM_JOURNAL: Journal ad0s1f clean.

<prompt>#</prompt> <userinput>mount -a</userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<emphasis>(boot continues)</emphasis> 		<prompt>#</prompt> <userinput>gjournal load</userinput>

GEOM_JOURNAL: Journal 2948326772: ad0s1g contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1h contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1d contains data.
GEOM_JOURNAL: Journal ad0s1d clean.
GEOM_JOURNAL: Journal 2948326772: ad0s1f contains data.
GEOM_JOURNAL: Journal ad0s1f clean.

<prompt>#</prompt> <userinput>mount -a</userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<emphasis>(boot continues)</emphasis>
If, on the other hand, this entry is correct, have a look at <filename>/etc/fstab</filename>. You will probably find a misspelled or missing entry. In this case, mount all remaining partitions by hand and continue with the multi-user boot. Se, por outro lado, esta entrada estiver correta, dê uma olhada em <filename>/etc/fstab</filename>. Você provavelmente encontrará uma entrada incorreta ou faltando. Nesse caso, monte todas as partições restantes manualmente e continue com o boot em modo multi-usuários.
Can I remove journaling and return to my standard file system with Soft Updates? Posso remover o registro no journal e retornar ao meu sistema de arquivos padrão com o Soft Updates?
Sure. Use the following procedure, which reverses the changes. The partitions you created for the journal providers can then be used for other purposes, if you so wish. Certo. Use o procedimento a seguir, que inverte as alterações. As partições que você criou para os provedores de journal podem ser usadas para outros propósitos, se você desejar.
Login as <systemitem class="username">root</systemitem> and switch to single user mode: Faça login como <systemitem class="username"> root </systemitem> e alterne para o modo de usuário único:
Unmount the journaled partitions: Desmonte as partições journaled:
Synchronize the journals: Sincronize os journals:
<prompt>#</prompt> <userinput>gjournal sync</userinput> <prompt>#</prompt> <userinput>gjournal sync</userinput>
Stop the journaling providers: Pare os provedores de journaling:
<prompt>#</prompt> <userinput>gjournal stop ad0s1d.journal</userinput>
<prompt>#</prompt> <userinput>gjournal stop ad0s1f.journal</userinput> 		<prompt>#</prompt> <userinput>gjournal stop ad0s1d.journal</userinput>
<prompt>#</prompt> <userinput>gjournal stop ad0s1f.journal</userinput>
Clear journaling metadata from all the devices used: Limpe os metadados de journaling de todos os dispositivos usados:
<prompt>#</prompt> <userinput>gjournal clear ad0s1d</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1f</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1g</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1h</userinput> 		<prompt>#</prompt> <userinput>gjournal clear ad0s1d</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1f</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1g</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1h</userinput>
Clear the file system journaling flag, and restore the Soft Updates flag: Limpe o sinalizador de journaling do sistema de arquivos e restaure a flag do Soft Updates:
<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1d</userinput>

tunefs: gjournal cleared
tunefs: soft updates set

<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1f</userinput>

tunefs: gjournal cleared
tunefs: soft updates set 		<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1d</userinput>

tunefs: gjournal cleared
tunefs: soft updates set

<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1f</userinput>

tunefs: gjournal cleared
tunefs: soft updates set
Remount the old devices by hand: Remonte os dispositivos antigos à mão:
<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1d /var</userinput>
<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1f /usr</userinput> 		<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1d /var</userinput>
<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1f /usr</userinput>

Loading…

No matching activity found.

Browse all component changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: answer/screen
Flags
no-wrap
Source string location
article.translate.xml:551
String age
a year ago
Source string age
a year ago
Translation file
articles/pt_BR/gjournal-desktop.po, string 111