On Mon, Jun 03, 2019 at 09:06:11PM -0700, Ross Boylan wrote:
>
> Takeaways:
> * Don't say 4TB when you mean 4GB! (Duh)
> * e2fs tools report (roughly?) the entire device size for block count,
> while df only shows the size of the data area, excluding metadata
> * Mis-sized journals can be fixed by
Le 03/06/2019 à 19:36, Ross Boylan a écrit :
I just noticed the reported journal size is exactly 1G, which would
account for the difference:
Journal size: 1024M
That's assuming the units are bytes; if they are blocks, it's just a
crazy value.
Sounds interesting. Here on a ~4 GiB ext
On Mon, Jun 3, 2019 at 10:36 AM I wrote:
>
> I just noticed the reported journal size is exactly 1G, which would
> account for the difference:
> Journal size: 1024M
> That's assuming the units are bytes; if they are blocks, it's just a
> crazy value.
>
> I'll see what the extN experts h
I just noticed the reported journal size is exactly 1G, which would
account for the difference:
Journal size: 1024M
That's assuming the units are bytes; if they are blocks, it's just a
crazy value.
I'll see what the extN experts have to say.
Ross
# ls -l /dev/mapper/vgbarley-cache /dev/vgbarley/cache
lrwxrwxrwx 1 root root 8 Jun 1 17:26 /dev/mapper/vgbarley-cache -> ../dm-19
lrwxrwxrwx 1 root root 8 Jun 1 17:26 /dev/vgbarley/cache -> ../dm-19
On Mon, Jun 3, 2019 at 2:32 AM Henning Follmann
wrote:
>
> You cheat ;)
> please show that
>
>
On Sat, Jun 01, 2019 at 02:46:00PM -0700, Ross Boylan wrote:
> # df -B4096 /var/local/cache/
> Filesystem 4K-blocks Used Available Use% Mounted on
> /dev/mapper/vgbarley-cache778160 191713529923 27% /var/local/cache
>
> # e2fsck -v /dev/vgbarley/cache
> e2fsck 1.44.5 (15
> If the filesystem and the volume manager both agree on 4GB, I don't
> know where df is getting the notion that it's 3GB. It seems very
Sure looks like a bug. I think reporting it as a bug to the ext234
people is The Right Thing to do.
Stefan
# e2fsck -v -f /dev/vgbarley/cache
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
8410 inodes used (6.42%, out o
On Sat, Jun 1, 2019 at 3:49 PM Gary Dale wrote:
>
> I suggest trying gparted to read the partition table on your drive.
> There may be a problem and gparted is usually pretty good at finding
> partition table errors.
>
Since the file system is sitting on an LVM logical volume, I don't
think the pa
I suggest trying gparted to read the partition table on your drive.
There may be a problem and gparted is usually pretty good at finding
partition table errors.
On 2019-06-01 1:41 p.m., Ross Boylan wrote:
df says my volume is 3G, but everything else says it's 4G. What's
going on and how can
Le 01/06/2019 à 23:46, Ross Boylan a écrit :
# e2fsck -v /dev/vgbarley/cache
e2fsck 1.44.5 (15-Dec-2018)
/dev/vgbarley/cache: clean, 8361/131072 files, 462129/1048576 blocks
You must specify -f for a complete check.
# df -B4096 /var/local/cache/
Filesystem 4K-blocks Used Available Use% Mounted on
/dev/mapper/vgbarley-cache778160 191713529923 27% /var/local/cache
# e2fsck -v /dev/vgbarley/cache
e2fsck 1.44.5 (15-Dec-2018)
/dev/vgbarley/cache: clean, 8361/131072 files, 462129/1048576
Le 01/06/2019 à 19:41, Ross Boylan a écrit :
df says my volume is 3G, but everything else says it's 4G. What's
going on and how can I correct it?
Did you try e2fsck ?
On Sat, Jun 01, 2019 at 10:41:20AM -0700, Ross Boylan wrote:
> df says my volume is 3G, but everything else says it's 4G. What's
> going on and how can I correct it?
>
> This question concerns the total reported space, not the free space.
>
> The volume is an LVM logical volume on buster with an
df says my volume is 3G, but everything else says it's 4G. What's
going on and how can I correct it?
This question concerns the total reported space, not the free space.
The volume is an LVM logical volume on buster with an ext4 file
system. I originally mistakenly created it as 4TB in size.
Th
15 matches
Mail list logo
