[Bug 480496] Re: "raid45: Invalid RAID device offset parameter" error after activating fake raid

[Krzysztof Limburski]

apport information

** Tags added: apport-collected

** Description changed:

  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_Volume0
  size   : 3451069440
  stride : 256
  type   : stripe
  status : ok
  subsets: 0
  devs   : 3
  spares : 0
  --> Subset
  name   : isw_ebgeeadada_Volume1
  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_Volume0" already active
  RAID set "isw_ebgeeadada_Volume1" was not activated
  ...
  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.sectors_per_dev)
   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/controlC1:  limbur     2370 F.... pulseaudio
+  /dev/snd/controlC0:  limbur     2370 F.... pulseaudio
+ 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,1458a002,00100101'
+    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=UUID=8cc83280-f0e0-4329-aff8-6b790828ad76
+ IwConfig:
+  lo        no wireless extensions.
+  
+  eth0      no wireless extensions.
+ MachineType: Gigabyte Technology Co., Ltd. EP35-DS4
+ NonfreeKernelModules: nvidia
+ Package: linux 2.6.32.22.23
+ PackageArchitecture: amd64
+ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=595bdc1b-bfc9-4ce1-81b3-b572a877bd6e ro libata.ignore_hpa=0 crashkernel=384M-2G:64M,2G-:128M quiet splash
+ ProcEnviron:
+  LANG=pl_PL.utf8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
+ Regression: No
+ RelatedPackageVersions: linux-firmware 1.34
+ Reproducible: Yes
+ RfKill:
+  
+ Tags: lucid kconfig needs-upstream-testing
+ 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:bvnAwardSoftwareInternational,Inc.:bvrF6:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: EP35-DS4
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaDevices.txt"
   http://launchpadlibrarian.net/48168584/AlsaDevices.txt

-- 
"raid45: Invalid RAID device offset parameter" error after activating fake raid
https://bugs.launchpad.net/bugs/480496
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.