From Fedora Project Wiki
(Created page with "{{autolang}} <!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are...")
 
No edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{autolang}}
{{autolang}}
<!-- All fields on this form are required to be accepted by FESCo.
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->


<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
= BTRFS di Fedora 17 file system predefinito =


= Fedora 17 BTRFS default file system =
== Sommario ==
Rendere BTRFS il file system predefinito per installazioni normali.


== Summary ==
== Manutentore ==
Make BTRFS the default file system for normal installs.
* Nome: [[User:josef| Josef Bacik]]
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
 
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:josef| Josef Bacik]]
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Email: josef@redhat.com
* Email: josef@redhat.com


== Current status ==
== Status corrente ==
* Targeted release: [[Releases/17 | Fedora 17 ]]  
Consultare la sezione [[Features/F17BtrfsDefaultFs#Current status|Current status]]  
* Last updated: 2011-11-15
* Percentage of completion: 0%
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


== Detailed Description ==
== Descrizione dettagliata ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Rendere BTRFS il file system predefinito per nuove installazioni di Fedora, ed uso delle capacità di gestione di volume, integrate in BTRFS, al posto di LVM.
Make BTRFS the default file system for new installations of Fedora, and use BTRFS's built in volume management capabilities instead of LVM.


== Benefit to Fedora ==
== Vantaggi per Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
BTRFS include molte caratteristiche non presenti in altri file system, altamente apprezzati dai normali utenti, tra cui:
BTRFS includes many features that do not exist in any other file system that are highly valuable to normal users, including


* Checksumming
* Checksumming
* Snapshotting
* Snapshotting
* Built in volume management and RAID
* Gestione volumi integrato e RAID
 
Il checksumming offre agli utenti migliore integrità dei dati, e lo snapshotting permette di fare cose come prendere snapshot del file system prima di fare cose potenzialmente dannose, come gli aggiornamenti via yum, in modo da avere uno stato di a cui tornare.


Checksumming give our users better data integrity, and snapshotting allows us to do thing's like take snapshots of the file system before doing potentially dangerous things, like yum updates, in order to provide a position to roll back to.
== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
Fare riferimento alla [[Features/F17BtrfsDefaultFs#Scope |versione originale di questo documento]].
* Anaconda - not terribly important but would be good to expose some of the different features of BTRFS via anaconda.
** Subvolume support (for /home by default)
** Optional compression
** RAID support
** Ext3/4 conversion
* LiveCD tools - these would need to be reworked to create a BTRFS image to install with.


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Fare riferimento alla [[Features/F17BtrfsDefaultFs#How To Test |versione originale di questo documento]].
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
It should be simple enough to test, just do a normal install.  If Anaconda gets support for the different BTRFS capabilities we'd want to test a couple of cases
 
* Single disk BTRFS
* Multi-disk BTRFS, RAID0/1/10
* Creating different subvolumes in the install


== User Experience ==
== Esperienza utente ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Il cambiamento dovrebbe essere largamente invisibile agli utenti. Questi potranno trarre vantaggio dalle varie caratteristiche messe a disposizione di BTRFS.
The change should be largely invisible to users.  They will just be able to take advantage of the different features that BTRFS has if they so choose.


== Dependencies ==
== Dipendenze ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* Anaconda
* Anaconda
Line 78: Line 41:
== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
We can just keep ext4 as the default installed file system.
Fare riferimento alla [[Features/F17BtrfsDefaultFs#Contingency Plan |versione originale di questo documento]].


== Documentation ==
== Documentazione ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*[http://btrfs.wiki.kernel.org/ | Btrfs Wiki]
*[http://btrfs.wiki.kernel.org/ | Btrfs Wiki]


== Release Notes ==
== Note di rilascio ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
Al momento non c'è niente da specificare altro che si illumina la strada del cambiamento.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
There shouldn't be anything we need to specifically say other than hi-light the change.


== Comments and Discussion ==
== Commenti e Discussioni ==
* See [[Talk:Features/F17BtrfsDefaultFs]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/F17BtrfsDefaultFs]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=689509
* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=689509


[[Category:FeatureAcceptedF17]]
[[Category:FeatureAcceptedF17]]
[[Category:Italiano]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 10:39, 9 January 2012

BTRFS di Fedora 17 file system predefinito

Sommario

Rendere BTRFS il file system predefinito per installazioni normali.

Manutentore

Status corrente

Consultare la sezione Current status

Descrizione dettagliata

Rendere BTRFS il file system predefinito per nuove installazioni di Fedora, ed uso delle capacità di gestione di volume, integrate in BTRFS, al posto di LVM.

Vantaggi per Fedora

BTRFS include molte caratteristiche non presenti in altri file system, altamente apprezzati dai normali utenti, tra cui:

  • Checksumming
  • Snapshotting
  • Gestione volumi integrato e RAID

Il checksumming offre agli utenti migliore integrità dei dati, e lo snapshotting permette di fare cose come prendere snapshot del file system prima di fare cose potenzialmente dannose, come gli aggiornamenti via yum, in modo da avere uno stato di a cui tornare.

Scope

Fare riferimento alla versione originale di questo documento.

How To Test

Fare riferimento alla versione originale di questo documento.

Esperienza utente

Il cambiamento dovrebbe essere largamente invisibile agli utenti. Questi potranno trarre vantaggio dalle varie caratteristiche messe a disposizione di BTRFS.

Dipendenze

  • Anaconda
  • LiveCD tools

Contingency Plan

Fare riferimento alla versione originale di questo documento.

Documentazione

Note di rilascio

Al momento non c'è niente da specificare altro che si illumina la strada del cambiamento.

Commenti e Discussioni

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/F17BtrfsDefaultFs/it&oldid=265979"