Re: [bug #48685] update-grub triggers filesystem server panics

[Justus Winter]

"Brent W. Baccala"  writes:

> On Tue, Aug 2, 2016 at 9:52 PM, Justus Winter 
> wrote:
>
>>
>> The isofs crash is fixed in 21ee0e79.  Please update your Hurd packages.
>>
>> The fact that you are seeing these messages is a (quite nice actually)
>> side-effect of 234568d0.  I guess that if you were doing this on a Linux
>> machine, you would see these in the kernel ring buffer.
>>
>>
> OK, I updated my Hurd system using the Debian ports repository.  The
> package is hurd-0.8.git20160522, and it includes 21ee0e79.
>
> Sure enough, the crash is gone, but I still get the error messages:

Good.

> ext2fs: /dev/hd0s2: panic: main: device too small for superblock (1024
> bytes)
> /hurd/fatfs: Invalid number of bytes per sector
> /hurd/iso9660fs: Could not find valid superblock
>
> Are you suggesting that these are to be expected?

Yes.

> Is this a bug in update-grub?

No.

> These messages seem awfully severe for a standard system operation.

And as I demonstrated, the very same kind of messages are generated on a
Linux machine.  The filesystem servers open the Mach console and write
the messages there.  You just happen to work on a console where those
messages are relayed.  If you were to do update-grub from an xterm, you
wouldn't see these.

Cheers,
Justus


signature.asc
Description: PGP signature

Re: [bug #48685] update-grub triggers filesystem server panics

[Brent W. Baccala]

On Tue, Aug 2, 2016 at 9:52 PM, Justus Winter 
wrote:

>
> The isofs crash is fixed in 21ee0e79.  Please update your Hurd packages.
>
> The fact that you are seeing these messages is a (quite nice actually)
> side-effect of 234568d0.  I guess that if you were doing this on a Linux
> machine, you would see these in the kernel ring buffer.
>
>
OK, I updated my Hurd system using the Debian ports repository.  The
package is hurd-0.8.git20160522, and it includes 21ee0e79.

Sure enough, the crash is gone, but I still get the error messages:

ext2fs: /dev/hd0s2: panic: main: device too small for superblock (1024
bytes)
/hurd/fatfs: Invalid number of bytes per sector
/hurd/iso9660fs: Could not find valid superblock

Are you suggesting that these are to be expected?  Is this a bug in
update-grub?  These messages seem awfully severe for a standard system
operation.

agape
brent

[bug #48685] update-grub triggers filesystem server panics

[Justus Winter]

Update of bug #48685 (project hurd):

  Status:None => Fixed  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

The isofs crash is fixed in 21ee0e79.  Please update your Hurd packages.

The fact that you are seeing these messages is a (quite nice actually)
side-effect of 234568d0.  I guess that if you were doing this on a Linux
machine, you would see these in the kernel ring buffer.  And indeed, I just
tried:

[  667.337992] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device
dm-6.
[  667.339712] hfsplus: unable to find HFS+ superblock
[  667.341322] qnx4: no qnx4 filesystem (no root dir).
[  667.342771] ufs: You didn't specify the type of your ufs filesystem

mount -t ufs -o
ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
ufstype=old
[  667.342935] ufs: ufs_fill_super(): bad magic number
[  667.344509] hfs: can't find a HFS filesystem on dev dm-6


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[bug #48685] update-grub triggers filesystem server panics

[Brent Baccala]

URL:
  

 Summary: update-grub triggers filesystem server panics
 Project: The GNU Hurd
Submitted by: baccala
Submitted on: Wed 03 Aug 2016 07:01:57 AM GMT
Category: Hurd
Severity: 3 - Normal
Priority: 5 - Normal
  Item Group: None
  Status: None
 Privacy: Public
 Assigned to: None
 Originator Name: 
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Reproducibility: Every Time
  Size (loc): None
 Planned Release: None
  Effort: 0.00
Wiki-like text discussion box: 

___

Details:

I'm running Mach/Hurd in qemu/kvm, on a Linux 4.4.0 host (Ubuntu 16.04).  Mach
is 1.7+git20160607-486-dbg; the Hurd is from debian-hurd-20160325.

I always get panics when I run update-grub:


ext2fs: /dev/hd0s2: panic: main: device too small for superblock (1024 bytes)
/hurd/fatfs: Invalid number of bytes per sector
/hurd/crash: /hurd/iso9660fs --ro /dev/hd0s2(1432) crashed, signal {no:11,
code:1, error:1}, exception {1, code:1, subcode:241664}, PCs: {0x804aa5c,
0x11254fc, 0x11254fc, 0x10ccb10, 0x10ccb10}, killing task.


Here's what update-grub is reporting:


root@debian:~# update-grub
Generating grub configuration file ...
Warning: Requested serial terminal but GRUB_SERIAL_COMMAND is unspecified.
Default parameters will be used.
Found GNU Mach: /boot/gnumach-1.6-486.gz
Found GNU Mach: /boot/gnumach-1.7-486-dbg.gz
Found Hurd module: /hurd/ext2fs.static
Found Hurd module: /hurd/exec
done
root@debian:~#


/dev/hd0s2 is the extended partition:


DeviceBoot   Start End Sectors  Size Id Type
debian-hurd-20160325.img1 2048 5787647 5785600  2.8G 83 Linux
debian-hurd-20160325.img2  5789694 6143999  354306  173M  5 Extended
debian-hurd-20160325.img5  5789696 6143999  354304  173M 82 Linux swap /
Solaris


Looks to me like it's doing something to the extended partition, which seems
strange, and then bad things happen.





___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/