Martin writes:
> The smallest disk of the 122 is 500GB. Is it possible to have btrfs
> see each disk as only e.g. 10GB? That way I can corrupt and resilver
> more disks over a month.
Well, at least you can easily partition the devices for that to happen.
However, I would also suggest that would
Goffredo Baroncelli writes:
> Hi Anand,
>
>
> On 2015-09-17 17:18, Anand Jain wrote:
>> it looks like -o degraded is going to be a very obvious feature,
>> I have plans of making it a default feature, and provide -o
>> nodegraded feature instead. Thanks for comments if any.
>>
>> Thanks, Anan
Gareth Pye writes:
> People tend to be looking at BTRFS for a guarantee that data doesn't
> die when hardware does. Defaults that defeat that shouldn't be used.
However, data is no more in danger at startup than it is at the moment
when btrfs notices a drive dropping, yet it permits IO to procee
Lionel Bouton writes:
> 1/ AFAIK the kernel md RAID1 code behaves the same (last time I checked
> you need 2 processes to read from 2 devices at once) and I've never seen
> anyone arguing that the current md code is unstable.
This indeed seems to be the case on my MD RAID1 HDD.
But on MD SSD RA
audio muze writes:
> It seems to me that the simplest option at present is probably to use
> each disk separately, formatted btrfs, and backed up to other drives.
> The data to be stored on these drives is largely static - video and
> audio library.
In that case this might be applicaple to your
Hugo Mills writes:
>It has to be disabled because if you enable it, there's a race
> condition: since you're overwriting existing data (rather than CoWing
> it), you can't update the checksums atomically. So, in the interests
> of consistency, checksums are disabled.
I suppose this has been s
Austin S Hemmelgarn writes:
> And that is exactly the case with how things are now, when something
> is marked NOCOW, it has essentially zero guarantee of data consistency
> after a crash.
Yes. In addition to the zero guarantee of the data validity for the data
being written into, btrfs also doe
Hello,
Recently I added daily rebalancing to my cron.d (after finding myself in
the no-space-situation), and not long after that, I found my PC had
crashed over night. Having no sign in the logs anywhere (not even over
network even though there should be) I had nothing to go on, but this
night it
Hello,
Thanks for the super-fast response :).
I've installed the patch and shall be waiting. The effects should be
visible within a week given daily rebalances of two filesystems.
--
_
/ __// /__ __ h
Filipe Manana writes:
> Try this (just sent a few minutes ago):
> https://patchwork.kernel.org/patch/7463161/
I've been using this patch for a week now, doing two rebalances a day
(one per file system) - no problem so far. Thanks!
Probably unrelated to this I did experience one reboot without an
Martin writes:
> The *ONLY* application that I know of that uses atime is Mutt and then
> *only* for mbox files!...
However, users, such as myself :), can be interested in when a certain
file has been last accessed. With snapshots I can even get an idea of
all the times the file has been accesse
Igor M writes:
> Why btrfs becames EXTREMELY slow after some time (months) of usage ?
Have you tried iostat from sysstat to see the number of IO-operations
performed per second (tps) on the devices when it is performing badly?
If the number is hitting your seek rate (ie. 1/0.0075 for 7.5 ms see
Erkki Seppala writes:
> If the number is hitting your seek rate (ie. 1/0.0075 for 7.5 ms seek =
> 133), then fragmentation is sure to be blamed.
Actually the number may very well be off by at least a factor of two (I
tested that my device did 400 tps when I expected 200; perhaps bulk
tra
Austin S Hemmelgarn writes:
> Another thing that isn't listed there, that I would personally love to
> see is support for secure file deletion.
As discussed in the followups, it is difficult to do a really secure
deletion and a security-conscious person would opt to use encryption
instead. Abili
Robert White writes:
> You don't check your car's gas tank every time you put your foot on
> the brake, you don't want to check your free space every time your
> system finishes every tiny command you type.
Well, actually my car makes a bling every 10 km once it reaches <=80 km
range, and I don'
Robert White writes:
> You need to buy better disks. 8-)
Where can one buy these better disks with reasonable prices?-) Disks are
best thought of as consumables.
> I use SMART (smartmontools etc) and its tests to keep track of and
> warn me of such issues. It's way more likely to catch incipien
lu...@plaintext.sk writes:
Hello,
> luvar@blackdawn:~$ sudo time btrfs balance start -dconvert=raid1 -dusage=20
> /home/luvar/programs/
> Am I doing something forbidden (I have not see any structure where
> raid type is stored per file/subvolume item), or I just hit some
> problem? What should
Lutz Vieweg writes:
> Maybe "chattr +C" could print a warning if a file
> to change attributes for is > 0 bytes long?
This may only affect btrfs. The old ext2? ext3? compression patches
were able to compress pre-existing files. I don't know how other
filesystems behave in this regard.
--
___
Brendan Hide writes:
> Interesting case. I'm not sure of the merits/workaround needed to do
> this. It appears even using cat into netcat (nc) causes netcat to quit
> if you background the operation.
Well, that netcat has a bug doesn't mean btrfs-progs should have one as
well :) (though I didn't
K Richard Pixley writes:
> But as a user level facility, I want to be able to snapshot before
> making a change to a tree full of source code and (re)building it all
> over again. I may want to keep my new build, but I may want to flush
> it and return to known good state.
You may want to check
20 matches
Mail list logo
