Re: ext4 filesystem not recognised on new LVM volume

[John Lane]

On 15/12/14 11:51, Andrei Borzenkov wrote:
> On Mon, Dec 15, 2014 at 2:14 PM, John Lane <address@hidden> wrote:
>> I have this weird problem occurring today.
>>
>> I have a disk that has LVM on it with a number of logical volumes
>> containing ext4 filesystems.
>>
>> Grub has been able to see this disk and detect the ext4 filesystems
>> without issue.
>>
>> This morning, I added a new logical volume, formatted it ext4 and put a
>> system on it.
>>
>> Grub does not recognise the filesystem on the new volume. It sees the
>> volume fine but that's all.
>>
>> The new volume works fine on any Linux system I connect it to. Grub
>> still recognises the other volumes' filesystems fine, it's just the new
>> ones.
>>
>> I'm puzzled. Any suggestions as to what I can look it?
>>
> It could be that it is so new that some features are not supported by
> grub. Could you show output of "debugfs -R feature /dev/xxx" for this
> device?
>
output for volume that does not work and one that does (result for both
the same)

Filesystem features: has_journal ext_attr resize_inode dir_index
filetype extent flex_bg sparse_super large_file huge_file uninit_bg
dir_nlink extra_isize
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype extent flex_bg sparse_super large_file huge_file uninit_bg
dir_nlink extra_isize

some other details.

It's a 4Tb drive. There are 21 volumes on it now. "lvdisplay" examaple
below...


 --- Logical volume ---
  LV Path                /dev/bench/testing
  LV Name                bench-testing
  VG Name                bench
  LV UUID                FF65be-l2UX-61rU-AD5p-px0e-fN4m-55DQDK
  LV Write Access        read/write
  LV Creation host, time myhost, 2014-12-14 19:20:28 +0000
  LV Status              available
  # open                 0
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:15

I have just tried another disk from scratch and it worked fine.
I reformatted an existing volume and that was fine too.

I'm going to wipe the disk and start over and see if I can reproduce it.