On Wed, Dec 28, 2011 at 10:42 PM, Fajar A. Nugraha wrote:
> On Thu, Dec 29, 2011 at 11:37 AM, Roman Mamedov wrote:
>> On Thu, 29 Dec 2011 11:21:14 +0700
>> "Fajar A. Nugraha" wrote:
>>
>>> I'm trying fstrim and my disk is now pegged at write IOPS. Just
>>> wondering if maybe a "btrfs fi balance"
On Thu, Dec 29, 2011 at 11:37 AM, Roman Mamedov wrote:
> On Thu, 29 Dec 2011 11:21:14 +0700
> "Fajar A. Nugraha" wrote:
>
>> I'm trying fstrim and my disk is now pegged at write IOPS. Just
>> wondering if maybe a "btrfs fi balance" would be more useful, since:
> Modern controllers (like the San
On Thu, 29 Dec 2011 11:21:14 +0700
"Fajar A. Nugraha" wrote:
> Slightly off-topic, how useful would trim be for btrfs when using
> newer SSD which have their own garbage collection and wear leveling
> (e.g. sandforce-based)?
>
> I'm trying fstrim and my disk is now pegged at write IOPS. Just
> w
On Thu, Dec 29, 2011 at 11:21 AM, Fajar A. Nugraha wrote:
> I'm trying fstrim and my disk is now pegged at write IOPS. Just
> wondering if maybe a "btrfs fi balance" would be more useful,
Sorry, I meant "btrfs fi defrag"
--
Fajar
--
To unsubscribe from this list: send the line "unsubscribe linu
On Wed, Dec 28, 2011 at 11:57 PM, Martin Steigerwald
wrote:
> But BTRFS does not:
>
> merkaba:~> fstrim -v /
> /: 4431613952 bytes were trimmed
> merkaba:~> fstrim -v /
> /: 4341846016 bytes were trimmed
and apparently it can't trim everything. Or maybe my kernel is
just too old.
$ sudo fs
On Thu, Dec 29, 2011 at 11:02 AM, Li Zefan wrote:
> Martin Steigerwald wrote:
>> With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it
>> trimmed:
>> But BTRFS does not:
> There's no such plan, but it's do-able, and I can take care of it.
> There's an issue though.
> For btrfs
Martin Steigerwald wrote:
> Hi!
>
> With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it
> trimmed:
>
> merkaba:~> fstrim -v /boot
> /boot: 224657408 bytes were trimmed
> merkaba:~> fstrim -v /boot
> /boot: 0 bytes were trimmed
>
>
> But BTRFS does not:
>
> merkaba:~> fstrim
On Τετάρτη, 28 Δεκέμβριος 2011 11:48:32 μμ, Dave Chinner wrote:
On Wed, Dec 28, 2011 at 09:26:07PM +0200, Konstantinos Skarlatos wrote:
Hello all:
I have two machines with btrfs, that give me the "blocked for more
than 120 seconds" message. After that I cannot write anything to
disk, i am unable
On Wed, Dec 28, 2011 at 09:26:07PM +0200, Konstantinos Skarlatos wrote:
> Hello all:
> I have two machines with btrfs, that give me the "blocked for more
> than 120 seconds" message. After that I cannot write anything to
> disk, i am unable to unmount the btrfs filesystem and i can only
> reboot wi
Well now machine2 has just crashed too...
http://pastebin.com/gvfUm0az
On Τετάρτη, 28 Δεκέμβριος 2011 9:26:07 μμ, Konstantinos Skarlatos wrote:
Hello all:
I have two machines with btrfs, that give me the "blocked for more
than 120 seconds" message. After that I cannot write anything to disk,
i
Hello all:
I have two machines with btrfs, that give me the "blocked for more than
120 seconds" message. After that I cannot write anything to disk, i am
unable to unmount the btrfs filesystem and i can only reboot with
sysrq-trigger.
It always happens when i write many files with rsync over
Hi!
With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it
trimmed:
merkaba:~> fstrim -v /boot
/boot: 224657408 bytes were trimmed
merkaba:~> fstrim -v /boot
/boot: 0 bytes were trimmed
But BTRFS does not:
merkaba:~> fstrim -v /
/: 4431613952 bytes were trimmed
merkaba:~> fstri
12 matches
Mail list logo
