RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 847446 - Directory dmraid.ddf1 in run place
Summary: Directory dmraid.ddf1 in run place
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sos
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Bryn M. Reeves
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-11 11:04 UTC by Ivan
Modified: 2013-07-25 13:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-25 13:02:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ivan 2012-08-11 11:04:53 UTC 
Description of problem:
Created Directory instead inside archive

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


How reproducible:
[root@iwdb ~]# mkdir sos
[root@iwdb ~]# cd sos
[root@iwdb sos]# ls -la
итого 8
drwxr-xr-x   2 root root 4096 Авг 11 15:00 .
dr-xr-x---. 13 root root 4096 Авг 11 15:00 ..
[root@iwdb sos]# sosreport --batch

sosreport (version 2.2)

This utility will collect some detailed  information about the
hardware and setup of your Red Hat Enterprise Linux system.
The information is collected and an archive is  packaged under
/tmp, which you can send to a support representative.
Red Hat Enterprise Linux will use this information for diagnostic purposes ONLY
and it will be considered confidential information.

This process may take a while to complete.
No changes will be made to your system.


  Выполняются модули. Пожалуйста, подождите...

  Completed [51/51] ...      
Создаётся архив...

Созданный отчёт сохранен в: 
  /tmp/sosreport-iwdb-20120811150056-6e52.tar.xz

The md5sum is: a45d945d7d6cd730e5f06aad05796e52

Отправьте этот файл представителю службы поддержки.

[root@iwdb sos]# ls -la
итого 12
drwxr-xr-x   3 root root 4096 Авг 11 15:00 .
dr-xr-x---. 13 root root 4096 Авг 11 15:00 ..
drwxr-xr-x   2 root root 4096 Авг 11 15:00 dmraid.ddf1

Steps to Reproduce:
1. run sosreport --batch
2. ls -la
3.
  
Actual results:
Directory dmraid.ddf1 exist

Expected results:
Directory inside archive /tmp/sosreport*.tar.xz

Additional info:
Comment 4 RHEL Program Management 2012-12-14 08:50:11 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Bryn M. Reeves 2013-07-25 13:02:27 UTC 
Unable to reproduce and this appears to be a dmraid bug - please re-file against that component if you are still experiencing the problem.
Note You need to log in before you can comment on or make changes to this bug.