On Mon, Apr 02, 2018 at 10:07:01PM +, Hugo Mills wrote:
> On Mon, Apr 02, 2018 at 06:03:00PM -0400, Fedja Beader wrote:
> > Is there some testing utility for this? Is there a way to extract this/tell
> > with a high enough certainty from datasheets/other material before purchase?
>
>
On Mon, Apr 02, 2018 at 06:03:00PM -0400, Fedja Beader wrote:
> Is there some testing utility for this? Is there a way to extract this/tell
> with a high enough certainty from datasheets/other material before purchase?
Given that not implementing barriers is basically a bug in the
hardware
Is there some testing utility for this? Is there a way to extract this/tell
with a high enough certainty from datasheets/other material before purchase?
https://btrfs.wiki.kernel.org/index.php/FAQ#How_does_this_happen.3F
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
Hi,
I've updated the Status page and synced the manual pages from
btrfs-progs git.
The status of various features is split to one more column, Performance.
There's a section for each 'mostly OK' status below the table and linked
from the note. This will hopefully be more understandable than just
On Tue, Sep 12, 2017 at 09:19:14AM +, Alberto Bursi wrote:
> Since zstd was added in btrfs there are people wondering why not lz4 too.
>
> The wiki paragraph [1] cites a couple dead links as explanations on why
> it's not a good idea to have lz4 in btrfs.
Regarding dead li
On Tue, Sep 12, 2017 at 12:33:21PM +0300, Timofey Titovets wrote:
> 2017-09-12 12:19 GMT+03:00 Alberto Bursi <alberto.bu...@outlook.it>:
> > Since zstd was added in btrfs there are people wondering why not lz4 too.
> >
> > The wiki paragraph [1] cites a couple dead l
2017-09-12 12:19 GMT+03:00 Alberto Bursi <alberto.bu...@outlook.it>:
> Since zstd was added in btrfs there are people wondering why not lz4 too.
>
> The wiki paragraph [1] cites a couple dead links as explanations on why
> it's not a good idea to have lz4 in btrfs.
>
>
Since zstd was added in btrfs there are people wondering why not lz4 too.
The wiki paragraph [1] cites a couple dead links as explanations on why
it's not a good idea to have lz4 in btrfs.
I think it would be nice if someone can write that information back in
the wiki, or for the very least
On Wed, May 31, 2017 at 01:46:17PM +0200, David Sterba wrote:
> On Wed, May 31, 2017 at 07:35:24PM +0800, chou Dai wrote:
> > Hi,I wanted to add some content and edit some content to wiki,but I
> > made a registration two week ago(Account Name:Dai chou) . Now, I still
> > can
On Wed, May 31, 2017 at 07:35:24PM +0800, chou Dai wrote:
> Hi,I wanted to add some content and edit some content to wiki,but I
> made a registration two week ago(Account Name:Dai chou) . Now, I still
> cannot register, through registration request expired already. And
> Btrfs wiki sa
Hi,I wanted to add some content and edit some content to wiki,but I
made a registration two week ago(Account Name:Dai chou) . Now, I still
cannot register, through registration request expired already. And
Btrfs wiki says"Just drop a mail on linux kernel btrfs mailing list
with an approp
On Mon, Sep 19, 2016 at 01:38:36PM -0400, Austin S. Hemmelgarn wrote:
> >>I'm not sure if the brfsck is really all that helpful to user as much
> >>as it is for developers to better learn about the failure vectors of
> >>the file system.
> >
> >ReiserFS had no working fsck for all of the 8 years I
On 2016-09-19 14:27, Chris Murphy wrote:
On Mon, Sep 19, 2016 at 11:38 AM, Austin S. Hemmelgarn
wrote:
ReiserFS had no working fsck for all of the 8 years I used it (and still
didn't last year when I tried to use it on an old disk). "Not working"
here means "much less
On Mon, Sep 19, 2016 at 11:38 AM, Austin S. Hemmelgarn
wrote:
>> ReiserFS had no working fsck for all of the 8 years I used it (and still
>> didn't last year when I tried to use it on an old disk). "Not working"
>> here means "much less data is readable from the filesystem
On 2016-09-19 00:08, Zygo Blaxell wrote:
On Thu, Sep 15, 2016 at 01:02:43PM -0600, Chris Murphy wrote:
Right, well I'm vaguely curious why ZFS, as different as it is,
basically take the position that if the hardware went so batshit that
they can't unwind it on a normal mount, then an fsck
On Mon, Sep 19, 2016 at 08:32:14AM -0400, Austin S. Hemmelgarn wrote:
> On 2016-09-18 23:47, Zygo Blaxell wrote:
> >On Mon, Sep 12, 2016 at 12:56:03PM -0400, Austin S. Hemmelgarn wrote:
> >>4. File Range Cloning and Out-of-band Dedupe: Similarly, work fine if the FS
> >>is healthy.
> >
> >I've
On Mon, Sep 19, 2016 at 12:08:55AM -0400, Zygo Blaxell wrote:
>
> At the end of the day I'm not sure fsck really matters. If the filesystem
> is getting corrupted enough that both copies of metadata are broken,
> there's something fundamentally wrong with that setup (hardware bugs,
> software
On 2016-09-18 22:57, Zygo Blaxell wrote:
On Fri, Sep 16, 2016 at 08:00:44AM -0400, Austin S. Hemmelgarn wrote:
To be entirely honest, both zero-log and super-recover could probably be
pretty easily integrated into btrfs check such that it detects when they
need to be run and does so. zero-log
On 2016-09-18 23:47, Zygo Blaxell wrote:
On Mon, Sep 12, 2016 at 12:56:03PM -0400, Austin S. Hemmelgarn wrote:
4. File Range Cloning and Out-of-band Dedupe: Similarly, work fine if the FS
is healthy.
I've found issues with OOB dedup (clone/extent-same):
1. Don't dedup data that has not been
On Thu, Sep 15, 2016 at 01:02:43PM -0600, Chris Murphy wrote:
> Right, well I'm vaguely curious why ZFS, as different as it is,
> basically take the position that if the hardware went so batshit that
> they can't unwind it on a normal mount, then an fsck probably can't
> help either... they still
On Mon, Sep 12, 2016 at 12:56:03PM -0400, Austin S. Hemmelgarn wrote:
> 4. File Range Cloning and Out-of-band Dedupe: Similarly, work fine if the FS
> is healthy.
I've found issues with OOB dedup (clone/extent-same):
1. Don't dedup data that has not been committed--either call fsync()
on it, or
On Fri, Sep 16, 2016 at 08:00:44AM -0400, Austin S. Hemmelgarn wrote:
> To be entirely honest, both zero-log and super-recover could probably be
> pretty easily integrated into btrfs check such that it detects when they
> need to be run and does so. zero-log has a very well defined situation in
>
On 2016-09-15 17:23, Christoph Anton Mitterer wrote:
On Thu, 2016-09-15 at 14:20 -0400, Austin S. Hemmelgarn wrote:
3. Fsck should be needed only for un-mountable filesystems. Ideally,
we
should be handling things like Windows does. Preform slightly
better
checking when reading data, and if
On 2016-09-15 16:26, Chris Murphy wrote:
On Thu, Sep 15, 2016 at 2:16 PM, Hugo Mills wrote:
On Thu, Sep 15, 2016 at 01:02:43PM -0600, Chris Murphy wrote:
On Thu, Sep 15, 2016 at 12:20 PM, Austin S. Hemmelgarn
wrote:
2. We're developing new features
On Thu, 2016-09-15 at 14:20 -0400, Austin S. Hemmelgarn wrote:
> 3. Fsck should be needed only for un-mountable filesystems. Ideally,
> we
> should be handling things like Windows does. Preform slightly
> better
> checking when reading data, and if we see an error, flag the
> filesystem
> for
On Thu, Sep 15, 2016 at 2:16 PM, Hugo Mills wrote:
> On Thu, Sep 15, 2016 at 01:02:43PM -0600, Chris Murphy wrote:
>> On Thu, Sep 15, 2016 at 12:20 PM, Austin S. Hemmelgarn
>> wrote:
>>
>> > 2. We're developing new features without making sure that check
On Thu, Sep 15, 2016 at 01:02:43PM -0600, Chris Murphy wrote:
> On Thu, Sep 15, 2016 at 12:20 PM, Austin S. Hemmelgarn
> wrote:
>
> > 2. We're developing new features without making sure that check can fix
> > issues in any associated metadata. Part of merging a new
On Thu, Sep 15, 2016 at 12:20 PM, Austin S. Hemmelgarn
wrote:
> 2. We're developing new features without making sure that check can fix
> issues in any associated metadata. Part of merging a new feature needs to
> be proving that fsck can handle fixing any issues in the
On 2016-09-15 14:01, Chris Murphy wrote:
On Tue, Sep 13, 2016 at 5:35 AM, Austin S. Hemmelgarn
wrote:
On 2016-09-12 16:08, Chris Murphy wrote:
- btrfsck status
e.g. btrfs-progs 4.7.2 still warns against using --repair, and lists
it under dangerous options also; while
On Tue, Sep 13, 2016 at 5:35 AM, Austin S. Hemmelgarn
wrote:
> On 2016-09-12 16:08, Chris Murphy wrote:
>>
>> - btrfsck status
>> e.g. btrfs-progs 4.7.2 still warns against using --repair, and lists
>> it under dangerous options also; while that's true, Btrfs can't be
>>
On Mon, Sep 12, 2016 at 02:44:35PM -0600, Chris Murphy wrote:
> Just to cut yourself some slack, you could skip 3.14 because it's EOL
> now, and just go from 4.4.
Don't the btrfs-tools used to create the filesystem also play a huge
role in this game?
Greetings
Marc
--
Am Dienstag, 13. September 2016, 07:28:38 CEST schrieb Austin S. Hemmelgarn:
> On 2016-09-12 16:44, Chris Murphy wrote:
> > On Mon, Sep 12, 2016 at 2:35 PM, Martin Steigerwald
wrote:
> >> Am Montag, 12. September 2016, 23:21:09 CEST schrieb Pasi Kärkkäinen:
> >>> On Mon, Sep
On 2016-09-12 16:08, Chris Murphy wrote:
On Mon, Sep 12, 2016 at 10:56 AM, Austin S. Hemmelgarn
wrote:
Things listed as TBD status:
1. Seeding: Seems to work fine the couple of times I've tested it, however
I've only done very light testing, and the whole feature is
16, 18:27:47 CEST schrieb David Sterba:
On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
I therefore would like to propose that some sort of feature /
stability
matrix for the latest kernel is added to the wiki preferably
somewhere
where it is easy to find. It would be nice to archi
On 2016-09-13 04:38, Timofey Titovets wrote:
https://btrfs.wiki.kernel.org/index.php/Status
I suggest to mark RAID1/10 as 'mostly ok'
as on btrfs RAID1/10 is safe to data, but not for application that uses it.
i.e. it not hide I/O error even if it's can be masked.
https://btrfs.wiki.kernel.org/index.php/Status
I suggest to mark RAID1/10 as 'mostly ok'
as on btrfs RAID1/10 is safe to data, but not for application that uses it.
i.e. it not hide I/O error even if it's can be masked.
https://www.spinics.net/lists/linux-btrfs/msg56739.html
/* Retest it with
Pasi Kärkkäinen wrote:
On Mon, Sep 12, 2016 at 09:57:17PM +0200, Martin Steigerwald wrote:
Great.
I made to minor adaption. I added a link to the Status page to my warning in
before the kernel log by feature page. And I also mentioned that at the time
the page was last updated the latest
EST schrieb David Sterba:
>> > > On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
>> > > > > I therefore would like to propose that some sort of feature /
>> > > > > stability
>> > > > > matrix for the latest kernel is added
wrote:
> > > > > I therefore would like to propose that some sort of feature /
> > > > > stability
> > > > > matrix for the latest kernel is added to the wiki preferably
> > > > > somewhere
> > > > > where it is easy to find. It wou
bility
> > > > matrix for the latest kernel is added to the wiki preferably somewhere
> > > > where it is easy to find. It would be nice to archive old matrix'es as
> > > > well in case someone runs on a bit older kernel (we who use Debian tend
> > > >
On Mon, Sep 12, 2016 at 10:56 AM, Austin S. Hemmelgarn
wrote:
>
> Things listed as TBD status:
> 1. Seeding: Seems to work fine the couple of times I've tested it, however
> I've only done very light testing, and the whole feature is pretty much
> undocumented.
Mostly OK.
Am Montag, 12. September 2016, 18:27:47 CEST schrieb David Sterba:
> On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
> > > I therefore would like to propose that some sort of feature / stability
> > > matrix for the latest kernel is added to the wiki preferably
eature / stability
matrix for the latest kernel is added to the wiki preferably somewhere
where it is easy to find. It would be nice to archive old matrix'es as
well in case someone runs on a bit older kernel (we who use Debian tend
to like older kernels). In my opinion it would make things bit
some sort of feature / stability
>>>> matrix for the latest kernel is added to the wiki preferably somewhere
>>>> where it is easy to find. It would be nice to archive old matrix'es as
>>>> well in case someone runs on a bit older kernel (we who use Debian tend
>>&g
On 2016-09-12 12:27, David Sterba wrote:
On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
I therefore would like to propose that some sort of feature / stability
matrix for the latest kernel is added to the wiki preferably somewhere
where it is easy to find. It would be nice
On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
> > I therefore would like to propose that some sort of feature / stability
> > matrix for the latest kernel is added to the wiki preferably somewhere
> > where it is easy to find. It would be nice to arc
On Mon, Apr 25, 2016 at 08:06:47AM -0400, Nicholas D Steeves wrote:
> On 25 April 2016 at 07:36, David Sterba wrote:
> > The conversion looks relatively ok, indentation could be 2 spaces and
> > all bullet lists with '*'. Thanks.
>
> Done. I also added one line before each new
On 25 April 2016 at 07:36, David Sterba wrote:
> The conversion looks relatively ok, indentation could be 2 spaces and
> all bullet lists with '*'. Thanks.
Done. I also added one line before each new version. I've attached
it, since it's just one file; however, if you prefer I
rfs-progs
> >> changelog is located
> >
> > At the moment it's the release announcement in this mailinglist, that
> > gets copied to the wiki with some formatting adjustments. I'm willing to
> > copy the announcement text to a file in git (and will do for the next
oops, that gzip -9 shouldn't be there :-/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ncement in this mailinglist, that
> gets copied to the wiki with some formatting adjustments. I'm willing to
> copy the announcement text to a file in git (and will do for the next
> release). But at the moment I won't add all the past changelogs so if
> anybody wants to do that I'l appr
On Fri, Apr 22, 2016 at 08:41:36PM -0400, Nicholas D Steeves wrote:
> I'm just wondering where the primary location of the btrfs-progs
> changelog is located, because I'd like to include upstream changes in
> the Debian package. Is it really the wiki? If so, it would seem my
Nicholas D Steeves posted on Fri, 22 Apr 2016 20:41:36 -0400 as excerpted:
> I'm just wondering where the primary location of the btrfs-progs
> changelog is located, because I'd like to include upstream changes in
> the Debian package. Is it really the wiki? If so, it would seem my
Hi,
I'm just wondering where the primary location of the btrfs-progs
changelog is located, because I'd like to include upstream changes in
the Debian package. Is it really the wiki? If so, it would seem my
options are copying+pasting with every release, or writing a script to
download the page
one more tool for incremental backups to wiki, but
accidentally had typo in email at registration.
Now, more than one month after I still can't register, though
registration request should expire already.
Does anyone have access to fix that? Can't find any contacts of person
who supports wiki
On Sat, Aug 29, 2015 at 03:21:53AM +0200, Nazar Mokrynskyi wrote:
I wanted to add one more tool for incremental backups to wiki, but
accidentally had typo in email at registration.
Now, more than one month after I still can't register, though
registration request should expire already.
Does
I wanted to add one more tool for incremental backups to wiki, but
accidentally had typo in email at registration.
Now, more than one month after I still can't register, though
registration request should expire already.
Does anyone have access to fix that? Can't find any contacts of person
who
I wanted to add one more tool for incremental backups to wiki, but
accidentally had typo in email at registration.
Now, more than one month after I still can't register, though
registration request should expire already.
Does anyone have access to fix that? Can't find any contacts of person
who
On Sat, Aug 01, 2015 at 02:48:41PM -0600, Chris Murphy wrote:
On Sat, Aug 1, 2015 at 2:42 PM, Hugo Mills h...@carfax.org.uk wrote:
On Sat, Aug 01, 2015 at 11:29:40AM -0600, Chris Murphy wrote:
Does someone with wiki edit capability want to put up a warning about
btrfs-convert problems? I
Does someone with wiki edit capability want to put up a warning about
btrfs-convert problems? I don't think it needs to be a lengthy write
up since the scope of the problem is not clear yet. But since there's
definitely reproduced problems that have been going on for some time
now maybe it'd
On Sat, Aug 1, 2015 at 2:42 PM, Hugo Mills h...@carfax.org.uk wrote:
On Sat, Aug 01, 2015 at 11:29:40AM -0600, Chris Murphy wrote:
Does someone with wiki edit capability want to put up a warning about
btrfs-convert problems? I don't think it needs to be a lengthy write
up since the scope
On Sat, Aug 01, 2015 at 11:29:40AM -0600, Chris Murphy wrote:
Does someone with wiki edit capability want to put up a warning about
btrfs-convert problems? I don't think it needs to be a lengthy write
up since the scope of the problem is not clear yet. But since there's
definitely reproduced
On Mon, Jul 13, 2015 at 07:33:13PM +0200, Marc Joliet wrote:
Am Mon, 13 Jul 2015 19:21:54 +0200
schrieb Marc Joliet mar...@gmx.de:
OK, I'll make the changes then (sans kernel log).
Just a heads up: I accepted the terms of service, but the link goes to a
non-existent wiki page.
I have
Am Mon, 13 Jul 2015 06:56:17 + (UTC)
schrieb Duncan 1i5t5.dun...@cox.net:
Marc Joliet posted on Sun, 12 Jul 2015 14:26:04 +0200 as excerpted:
I hope it's not out of place, but I have a few suggestions for the Wiki:
Just in case it wasn't obvious... The wiki is open to user editing
Am Mon, 13 Jul 2015 19:21:54 +0200
schrieb Marc Joliet mar...@gmx.de:
OK, I'll make the changes then (sans kernel log).
Just a heads up: I accepted the terms of service, but the link goes to a
non-existent wiki page.
--
Marc Joliet
--
People who think they know everything really annoy those
:
I hope it's not out of place, but I have a few suggestions for the Wiki:
Just in case it wasn't obvious... The wiki is open to user editing. You
can, if you like, get an account and make the changes yourself. =:^)
Of course, it's understandable if your reaction to web and wiki
On Mon, Jul 13, 2015 at 01:18:27PM +0200, Marc Joliet wrote:
Am Mon, 13 Jul 2015 06:56:17 + (UTC)
schrieb Duncan 1i5t5.dun...@cox.net:
Marc Joliet posted on Sun, 12 Jul 2015 14:26:04 +0200 as excerpted:
I hope it's not out of place, but I have a few suggestions for the Wiki
Marc Joliet posted on Sun, 12 Jul 2015 14:26:04 +0200 as excerpted:
I hope it's not out of place, but I have a few suggestions for the Wiki:
Just in case it wasn't obvious... The wiki is open to user editing. You
can, if you like, get an account and make the changes yourself. =:^)
Of course
Hi,
I hope it's not out of place, but I have a few suggestions for the Wiki:
- The presentation NYLUG Presents: Chris Mason on Btrfs (May 14th 2015) at
https://www.youtube.com/watch?v=W3QRWUfBua8 would make a nice addition to the
Articles, presentations, podcasts section.
- The same goes
On the wiki, it first speaks about forcing compression by adding the c
attribute, but later states that the c attribute enables, not forces
compression. Which is it?
=from wiki:
Can I force compression on a file without using the compress mount option
Hi Dave,
you should forward your question directly to kernel.org webmaster
webmas...@kernel.org. They are using mediawiki in a multisite
environment for all kernel.org related wikis.
regards,
André
On 03/31/2015 04:00 AM, Dave Stevens wrote:
I've been reading the wiki to help sort out an issue
Stevens wrote:
I've been reading the wiki to help sort out an issue and learn more
about RAID. I wanted to download it to my local drive to read offlibe
and that facility sseems to not be there. I checked the mediawiki
version in the source and it is an LTS version for which support ends
in two
I've been reading the wiki to help sort out an issue and learn more
about RAID. I wanted to download it to my local drive to read offlibe
and that facility sseems to not be there. I checked the mediawiki
version in the source and it is an LTS version for which support ends
in two months
users know
the
correct timing using it.
I wonder about making a wiki page about recovery options with two
parts:
1) Diagnosis. First find out what might be wrong.
2) Cure. Then decide which steps to try to recover.
This seems really useful.
But I'm a little afraid
The wiki page https://btrfs.wiki.kernel.org/index.php/Mount_options has
outdated information regarding the metadata-ratio option.
It says:
metadata_ratio=number
Sets the number of data chunks that need to be allocated to force a
metadata chunk allocation. By default this is set to 8
documentation on the wiki.
* Play with your filesystems, work out how the FS behaves -- *in
detail*. Read the FS features on the wiki and try at least some of
them out. Use this to understand how it should behave. In
particular, the semantics of snapshots, and the difference between
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo Mills:
I am not asking to hold my hand
You are, though. Something like using grep to find code that (might
be) related to the thing you're trying to work with is _fundamental_.
You should expect to be reading the code -- several
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo Mills:
I am not asking to hold my hand
You are, though. Something like using grep to find code that (might
be) related to the thing you're trying to work with is _fundamental_.
You should expect to be reading the code --
On Sat, Jul 26, 2014 at 7:07 AM, Wang Shilong wangshilong1...@gmail.com wrote:
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo Mills:
I am not asking to hold my hand
You are, though. Something like using grep to find code that (might
be) related to the thing you're trying to
On Jul 26, 2014, at 7:43 PM, Nick Krause xerofo...@gmail.com wrote:
On Sat, Jul 26, 2014 at 7:07 AM, Wang Shilong wangshilong1...@gmail.com
wrote:
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo Mills:
I am not asking to hold my hand
You are, though. Something like using
On Sat, Jul 26, 2014 at 10:05 PM, Chris Murphy li...@colorremedies.com wrote:
On Jul 26, 2014, at 7:43 PM, Nick Krause xerofo...@gmail.com wrote:
On Sat, Jul 26, 2014 at 7:07 AM, Wang Shilong wangshilong1...@gmail.com
wrote:
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo
On 7/26/14, 8:43 PM, Nick Krause wrote:
...
Fine then I guess I need to read the documentation and other things on my own.
Seems everyone here wants me to figure out everything on my own.
Hugo bent over backwards, twice, to give you very good advice. So did
Steven Rostedt on LKML. You
Hey brtfs devolopers.
I am new so I think this project,Implement new FALLOC_FL_* modes needs
more information for me to
write if for you guys. I am wondering what is fallocate and how you
want me to write this, define statements
or as functions in a certain file? I am not asking to hold my hand
On Tue, Jul 08, 2014 at 10:19:08PM +0200, Sjon Hortensius wrote:
I wrote a simple alternative for a script that is currently on the
btrfs wiki (for showing quotas) in bash instead of Python. I have
attempted to add this to the page but after entering the captcha 15
times my account
I wrote a simple alternative for a script that is currently on the
btrfs wiki (for showing quotas) in bash instead of Python. I have
attempted to add this to the page but after entering the captcha 15
times my account was rejected because of a missing bio. Maybe someone
can add this to https
On Wed, May 14, 2014 at 09:49:48AM +0100, Astro Xe wrote:
The content of the FAQ How much space will I get with my multi-device
configuration?
(https://btrfs.wiki.kernel.org/index.php/FAQ#How_much_space_will_I_get_with_my_multi-device_configuration.3F)
is currently wrong. The usable space
Add btrfs wiki page reference to btrfs-check/btrfsck, btrfs-restore and
btrfs-device as supplement.
Signed-off-by: Qu Wenruo quwen...@cn.fujitsu.com
---
Documentation/btrfs-check.txt | 5 +
Documentation/btrfs-device.txt | 10 --
Documentation/btrfs-restore.txt | 4
On Tue, Apr 15, 2014 at 03:04:51PM +0800, Qu Wenruo wrote:
Add btrfs wiki page reference to btrfs-check/btrfsck, btrfs-restore and
btrfs-device as supplement.
I'd rather avoid any references to 'btrfsck', it's been deprecated and
'btrfs check' should be used, thouth I'm sure there are enough
On Mon, Apr 14, 2014 at 09:16:44AM +0800, Qu Wenruo wrote:
Generally, would you agree to putting more links to the wiki in man pages
since man pages are not forever but sure take a long time to update on the
installed based and the wiki can be up to date for everyone right away?
(I'm
Original Message
Subject: Re: wiki vs man pages
From: Marc MERLIN m...@merlins.org
To: Qu Wenruo quwen...@cn.fujitsu.com
Date: 2014年04月14日 09:45
On Mon, Apr 14, 2014 at 09:16:44AM +0800, Qu Wenruo wrote:
Generally, would you agree to putting more links to the wiki in man
On Mon, Apr 07, 2014 at 07:17:31PM +0200, George Eleftheriou wrote:
Thank you too for the enlightenment. Not just now but so many times in
the past (just the compilation of your list interventions is a wiki in
its own right).
Me too, I've been meaning to create a wiki account for quite some
Hi together,
I'm new to the list and hope to be at the right place for the following
issue:
The wiki page
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#btrfs_kernel_module_git_repository
talks about integrating an existing local kernel clone (instance) by
adding it as a git
Thanks to all, who* answer.
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
swapon $swapfile
i just adding this to rc.local and this work good.
May be, add it to btrfs Wiki as temporary solution to using swap file?
I always thought Btrfs does not allow swap files on purpose, because it is
not
deadlock-proof when used in the swapping context.
It's more
karim.allah.ah...@gmail.com posted on Sat, 26 Oct 2013 10:30:18 +0100 as
excerpted:
Is the swap over NFS code upstream ?
?esrever ni txet referp uoy od ;tsop-pot t'nod esaelP
(Please don't top-post; do you prefer text in reverse?)
Quote the context you need so your question makes sense and
#create 8G sparse swap file
losetup $swapfile /swap #mount file to loop
mkswap $swapfile
swapon $swapfile
i just adding this to rc.local and this work good.
May be, add it to btrfs Wiki as temporary solution to using swap file?
Timofey
Hi,
Yes, Timofey, it does work. I tested the same over
loop device
truncate -s 8G /swap #create 8G sparse swap file
losetup $swapfile /swap #mount file to loop
mkswap $swapfile
swapon $swapfile
i just adding this to rc.local and this work good.
May be, add it to btrfs Wiki as temporary solution to using swap file?
I always thought Btrfs
#mount file to loop
mkswap $swapfile
swapon $swapfile
i just adding this to rc.local and this work good.
May be, add it to btrfs Wiki as temporary solution to using swap file?
Timofey
2013/10/21 Тимофей Титовец nefelim...@gmail.com:
Hello list, i know what btrfs don't support swap files.
I
On Mon, 7 Oct 2013 13:07:25 -0600, Chris Murphy wrote:
I think the wiki has descriptions for check_int and check_int_data reversed:
I've fixed it in the wiki. Thanks!
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
I think the wiki has descriptions for check_int and check_int_data reversed:
check_int (since 3.3)
Switch on integrity checker for data and metadata (if compiled in)
check_int_data (since 3.3)
Switch on integrity checker for data (if compiled in)
https://btrfs.wiki.kernel.org/index.php
1 - 100 of 174 matches
Mail list logo