On Fri, 8 Apr 2016 16:53:32 +0500
Roman Mamedov wrote:
> On Fri, 08 Apr 2016 20:36:26 +0900
> Tomasz Chmielewski wrote:
>
> > On 2016-02-08 20:24, Roman Mamedov wrote:
> >
> > >> Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
> > >>
On 2016-05-12 15:03, Tomasz Chmielewski wrote:
FYI, I'm still getting this with 4.5.3, which probably means the fix
was not yet included ("No space left" at snapshot time):
/var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC
LOG: could not close temporary statistics file
On 2016-04-08 20:53, Roman Mamedov wrote:
> Do you snapshot the parent subvolume which holds the databases? Can you
> correlate that perhaps ENOSPC occurs at the time of snapshotting? If
> yes, then
> you should try the patch https://patchwork.kernel.org/patch/7967161/
>
> (Too bad this was not
Roman Mamedov posted on Fri, 08 Apr 2016 16:53:32 +0500 as excerpted:
> It's not in 4.4.6 either. I don't know why it doesn't get included, or
> what we need to do. Last time I asked, it was queued:
> http://www.spinics.net/lists/linux-btrfs/msg52478.html But maybe that
> meant 4.5 or 4.6 only?
On 2016-04-08 20:53, Roman Mamedov wrote:
> Do you snapshot the parent subvolume which holds the databases? Can you
> correlate that perhaps ENOSPC occurs at the time of snapshotting? If
> yes, then
> you should try the patch https://patchwork.kernel.org/patch/7967161/
>
> (Too bad this was not
On Fri, 08 Apr 2016 20:36:26 +0900
Tomasz Chmielewski wrote:
> On 2016-02-08 20:24, Roman Mamedov wrote:
>
> >> Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
> >> often snapshots, and at times, there is heavy IO in many of them for
> >> extended periods
On 2016-02-08 20:24, Roman Mamedov wrote:
Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
often snapshots, and at times, there is heavy IO in many of them for
extended periods of time. btrfs is on HDDs.
Every few days I'm getting "no space left" in a container running
Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
often snapshots, and at times, there is heavy IO in many of them for
extended periods of time. btrfs is on HDDs.
Every few days I'm getting "no space left" in a container running mongo
3.2.1 database. Interestingly, haven't
On 2016-02-08 20:24, Roman Mamedov wrote:
On Mon, 08 Feb 2016 18:22:34 +0900
Tomasz Chmielewski wrote:
Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
often snapshots, and at times, there is heavy IO in many of them for
extended periods of time. btrfs is
On Mon, 08 Feb 2016 21:15:38 +0900
Tomasz Chmielewski wrote:
> With the last error, a snapshot was made at around 06:06
> "no space left" was reported on 06:14.
If you mean the log that you have posted in your original message, the ENOSPC
happened at 06:06 and 14 seconds, not
On Mon, 08 Feb 2016 18:22:34 +0900
Tomasz Chmielewski wrote:
> Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
> often snapshots, and at times, there is heavy IO in many of them for
> extended periods of time. btrfs is on HDDs.
>
>
> Every few days I'm
How can I detect how much free space is left on a btrfs-volume?
As I read (and learned in practice!) df reports cannot be trusted if used on
btrfs-volumes.
Greetings, Michael
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
On Saturday 16 January 2010, Michael Niederle wrote:
How can I detect how much free space is left on a btrfs-volume?
As I read (and learned in practice!) df reports cannot be trusted if used
on
btrfs-volumes.
Try btrfs-show
$ btrfs-show
Label: bar uuid:
Hi, Goffredo!
Try btrfs-show
Thanks for your advice!
btrfs-show works but it displays a lot of error message for non-btrfs devices:
btrfs-show
failed to read /dev/sdg
failed to read /dev/sdg1
failed to read /dev/sdg2
failed to read /dev/sdg3
failed to read /dev/sdg4
failed to read /dev/md1
On Saturday 16 January 2010, you (Dipl.-Ing. Michael Niederle) wrote:
Hi, Goffredo!
Try btrfs-show
Thanks for your advice!
btrfs-show works but it displays a lot of error message for non-btrfs
devices:
btrfs-show
failed to read /dev/sdg
failed to read /dev/sdg1
failed to read
Goffredo Baroncelli wrote:
Try btrfs-show
Ok:
$ mount
/dev/sdc on /media/452f782b-738a-4699-abfa-588eecab07ea type btrfs
(rw,nosuid,nodev,uhelper=devkit)
$ df
/dev/sdc 932G 6.7G 925G 1%
/media/452f782b-738a-4699-abfa-588eecab07ea
$ btrfs-show
failed to read /dev/sdb1
On Saturday 16 January 2010, you (Svein Erik Brostigen) wrote:
Goffredo Baroncelli wrote:
Try btrfs-show
Ok:
$ mount
/dev/sdc on /media/452f782b-738a-4699-abfa-588eecab07ea type btrfs
(rw,nosuid,nodev,uhelper=devkit)
$ df
/dev/sdc 932G 6.7G 925G 1%
On Saturday 16 January 2010, Mathieu Chouquet-Stringer wrote:
Hello,
kreij...@gmail.com (Goffredo Baroncelli) writes:
Try btrfs-show
[...]
How do you read this then:
Label: none uuid: 27fafa43-7ad0-4e8a-ada8-36f73ef8984c
Total devices 2 FS bytes used 79.63GB
Hello,
kreij...@gmail.com (Goffredo Baroncelli) writes:
Try btrfs-show
[...]
How do you read this then:
Label: none uuid: 27fafa43-7ad0-4e8a-ada8-36f73ef8984c
Total devices 2 FS bytes used 79.63GB
devid2 size 111.79GB used 111.01GB path /dev/sdb
devid1
19 matches
Mail list logo