Xavier Gnata posted on Sun, 26 May 2013 00:11:55 +0200 as excerpted:
> Nowdays, external hard drives are mounted automagically by kde, gnome or
> whatever else.
> How is it suppose to work with external hard drives using btrfs with
> compression?
> If a btrfs filesystem lzo-compressed is mounted w
>> I can get btrfs to throw a kernel bug easily by running btrfs fi defrag
>> on some files in 3.9.0:
>
> Thanks for reporting. It's a known bug (that ought to be fixed before
> the 3.9 release in fact).
I'm still getting a BUG in __tree_mod_log_rewind on kernels 3.9.2 and 3.10-rc2
when trying to
Am Samstag, 25. Mai 2013, 23:29:41 schrieb Leonidas Spyropoulos:
> On Sat, May 25, 2013 at 1:13 PM, Martin Steigerwald
> wrote:
> > Am Samstag, 25. Mai 2013, 03:58:12 schrieb Duncan:
> > [...]
> > And can be verified by:
> >
> > martin@merkaba:~> grep ssd /proc/mounts
> > /dev/mapper/merkaba-debi
Am Samstag, 25. Mai 2013, 14:13:07 schrieb Martin Steigerwald:
> The SSD is in use for about 2 years. I left about 25 GiB free of the 300 GB
> it
> has.
>
> merkaba:~> smartctl -a /dev/sda | grep Host
> 225 Host_Writes_32MiB 0x0032 100 100 000Old_age Always
>
> -
Data that already exists will only be compressed on re-write. You can
do it with btrfs fi defrag and a script that traverses the fs to call
defrag on every file. Another good way is the find command that has
been outlined here:
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Defragmenting_a_di
On Sat, May 25, 2013 at 1:13 PM, Martin Steigerwald wrote:
> Am Samstag, 25. Mai 2013, 03:58:12 schrieb Duncan:
> [...]
> And can be verified by:
>
> martin@merkaba:~> grep ssd /proc/mounts
> /dev/mapper/merkaba-debian / btrfs rw,noatime,compress=lzo,ssd,space_cache 0 0
> /dev/mapper/merkaba-debia
Hello list,
Nowdays, external hard drives are mounted automagically by kde, gnome or
whatever else.
How is it suppose to work with external hard drives using btrfs with
compression?
If a btrfs filesystem lzo-compressed is mounted without the
|compress=|xxx option then all the newly created fil
Am Samstag, 25. Mai 2013, 19:36:03 schrieb Martin Steigerwald:
> Hi!
>
> Now I got it myself what I read again and again on this mailinglist: During
> apt-get upgrade I get no space left on device.
>
> But there is:
>
> merkaba:~> df -hT /
> DateisystemTyp Größe Benutzt Verf. V
Hi!
Now I got it myself what I read again and again on this mailinglist: During
apt-get upgrade I get no space left on device.
But there is:
merkaba:~> df -hT /
DateisystemTyp Größe Benutzt Verf. Verw% Eingehängt auf
/dev/mapper/merkaba-debian btrfs 19G 14G 4,6G 76% /
There was a missing free() call against fs_info->super_copy
in several places:
1) close_ctree()
2) open_ctree_broken() on failure
3) __open_ctree_fd() on failure
Signed-off-by: Filipe David Borba Manana
---
btrfs-find-root.c |5 +++--
disk-io.c |6 --
2 files changed, 7 in
There was a missing free() call against fs_info->super_copy
in several places:
1) close_ctree()
2) open_ctree_broken() on failure
3) __open_ctree_fd() on failure
Filipe David Borba Manana (1):
Btrfs-progs: Add missing free() against fs_info->super_copy
btrfs-find-root.c |5 +++--
disk-i
There was a missing free() call against fs_info->super_copy
in several places:
1) close_ctree()
2) open_ctree_broken() on failure
3) __open_ctree_fd() on failure
Signed-off-by: Filipe David Borba Manana
---
btrfs-find-root.c |4 ++--
disk-io.c |5 +++--
2 files changed, 5 inse
There was a missing free() call against fs_info->super_copy
in several places:
1) close_ctree()
2) open_ctree_broken() on failure
3) __open_ctree_fd() on failure
Filipe David Borba Manana (1):
Btrfs-progs: Add missing free() against fs_info->super_copy
btrfs-find-root.c |4 ++--
disk-io
Martin Steigerwald posted on Sat, 25 May 2013 14:13:07 +0200 as excerpted:
> Am Samstag, 25. Mai 2013, 03:58:12 schrieb Duncan:
>> Leonidas Spyropoulos posted on Fri, 24 May 2013 23:38:17 +0100 as
>>
>> excerpted:
>> > On 24 May 2013 21:07, "cwillu" wrote:
>> >> No need to specify ssd, it's auto
Am Samstag, 25. Mai 2013, 03:58:12 schrieb Duncan:
> Leonidas Spyropoulos posted on Fri, 24 May 2013 23:38:17 +0100 as
>
> excerpted:
> > On 24 May 2013 21:07, "cwillu" wrote:
> >> No need to specify ssd, it's automatically detected.
> >
> > I'm not so sure it did detected. When I manually set i
Am Freitag, 24. Mai 2013, 06:13:04 schrieb Duncan:
> > 2) Due to snapshots I know have well snapshots for my backup. And even
> > on SSD for my /home. I am not yet creating those in an automated way,
> > but well I do use them.
>
> As I already mentioned the warning on the wiki, do be aware of the
Am Donnerstag, 23. Mai 2013, 18:41:11 schrieb George Mitchell:
> On 05/23/2013 09:08 AM, Martin Steigerwald wrote:
> > 3) As to my knowledge mount times of large partitions can be quite
> > long with ReiserFS 3.
>
> That may well be, but I certainly wouldn't consider btrfs mount times
> "fast" in
On Sat, 25 May 2013, Leonidas Spyropoulos wrote:
> I decided not to add the discard option and run the daily script from
> cron (fstrim) as I think there's a performance hit with the discard.
> It mainly depends on your hardware I think.
I experienced a massive performance hit from discard and tu
On Sat, May 25, 2013 at 4:58 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> Without going back to check the wiki, IIRC it was there that the /sys
> paths it checks for that detection are listed. Those paths are then
> based on what the drive itself claims. If it claims to be rotating
> storage...
I
19 matches
Mail list logo
