"raid45: Invalid RAID device offset parameter" error after activating fake raid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have found problem after upgrading Ubuntu from version 9.04 to 9.10. I can't get access to my RAID5 volume. I have three 750GB in one group which is split into two volumes:
Volume0, RAID0 ~ 1750 GB
Volume1, RAID5 ~ 300 GB
sudo dmraid -s -g
*** Superset
name : isw_ebgeeadada
size : 4395441159
stride : 0
type : GROUP
status : setup
subsets: 2
devs : 3
spares : 0
--> Active Subset
name : isw_ebgeeadada_
size : 3451069440
stride : 256
type : stripe
status : ok
subsets: 0
devs : 3
spares : 0
--> Subset
name : isw_ebgeeadada_
size : 629562624
stride : 128
type : raid5_la
status : ok
subsets: 0
devs : 3
spares : 0
When I try to activate my volumes using "sudo dmraid -ya" it gives me message:
RAID set "isw_ebgeeadada
RAID set "isw_ebgeeadada
...
and dmesg:
...
device-mapper: table: 252:10: raid45: Invalid RAID device offset parameter
device-mapper: ioctl: error adding target to table
...
After some investigation I found problem in "dm-raid45" module. In file dm-raid4-5.c in definition of function dev_params(...) stands:
/* Get offset and device. */
if (sscanf(argv[1], "%llu", &tmp) != 1 || tmp > rs->set.
TI_ERR("Invalid RAID device offset parameter");
It has no sense. In my case start offset of Voume1 (sored in tmp) equals 1150360584 follow of big Volume0 but Volume1 have only 314781312 sectors. It causes device offset parameter error. Off course it will work if first volume is smaller than second one. When I removed bad comparison:
/* Get offset and device. */
if (sscanf(argv[1], "%llu", &tmp) != 1)
TI_ERR("Invalid RAID device offset parameter");
everything starts working again like in previous Ubuntu version (before system upgrade). It would be nice If you add this fix to some of next kernel upgrade. It will prevent recompiling bad module.
Regards
Krzysztof
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc100000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,
Controls : 40
Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'Audigy2'/'SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xd000, irq 19'
Mixer name : 'SigmaTel STAC9750,51'
Components : 'AC97a:83847650'
Controls : 211
Simple ctrls : 46
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. EP35-DS4
NonfreeKernelMo
Package: linux 2.6.32.22.23
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=pl_PL.utf8
SHELL=/bin/bash
ProcVersionSign
Regression: No
RelatedPackageV
Reproducible: Yes
RfKill:
Tags: lucid kconfig needs-upstream-
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: EP35-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: EP35-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
description: | updated |
tags: | added: kernel-series-unknown |
tags: |
added: karmic removed: kernel-series-unknown |
Changed in linux (Ubuntu): | |
status: | Expired → Incomplete |
Hi Krzysztof,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 480496
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]