Bug 489068

Summary: OCZ Vertex SSD serial number too long for dmraid
Product: [Fedora] Fedora Reporter: Remy Maucherat <remm>
Component: dmraidAssignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: agk, bmr, dwysocha, hdegoede, heinzm, lvm-team, mbroz, prockai, remm
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-22 09:59:06 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Additional patch to be added to the RPM none

Description Remy Maucherat 2009-03-06 21:42:30 EST
Created attachment 334378 [details]
Additional patch to be added to the RPM

Description of problem:
The serial number of these SSDs are too long for dmraid.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Use dmraid with OCZ Vertex SSD
Actual results:

Expected results:
Correct handling of the serial number, even if it's long.

Additional info:
Verified the Fedora source, and it looks like it would be affected as well.
The attached patch ports the patch that Ubuntu has used to the dmraid-1.0.0.rc15 used in Fedora. Verified the RPM builds fine with it, but not actually tested (would need two of the SSDs).
Comment 1 Remy Maucherat 2009-03-11 20:34:08 EDT
Ping ? The report includes a ready-to-apply patch, which seems to fix a real issue (people who buy SSD often RAID 0 two or more small drives, since the chance of failure is very small and it hides their small sizes).
Comment 2 Hans de Goede 2009-04-22 09:59:06 EDT
Closing this as a dup of bug 490121, where some patches where thrown back and forward fixing this properly (note it is fixed in rawhide now).

*** This bug has been marked as a duplicate of bug 490121 ***