Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 09 Oct 2014 21:22:35 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 194279] New: teach dumpsys / savecore to use dumpdev's sectorsize
Message-ID:  <bug-194279-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194279

            Bug ID: 194279
           Summary: teach dumpsys / savecore to use dumpdev's sectorsize
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: rpokala@panasas.com

>From freebsd-hackers@, thread "Seeking reviewers for patch; PR 193873"[0]:

As mentioned in another thread ([1], [2]), I'm looking at dumping on systems w/
AF-4Kn drives (on a fairly old version of FreeBSD). Unfortunately, I'm not at
all familiar w/ the process. I'm going to pick at it a few more days, but will
probably end up having to punt and dumpsys onto a 512n or AF-512e device. But,
since you are refactoring all this code in -CURRENT anyway, I think it would be
awesome if you could look to the future and make it work w/o assuming that dump
device block size is DEV_BSIZE; it would be better to use the sector size, as
returned (for example) by ioctl(DIOCGSECTORSIZE).

[0]
https://lists.freebsd.org/pipermail/freebsd-hackers/2014-October/046217.html
[1]
https://lists.freebsd.org/pipermail/freebsd-hackers/2014-September/046164.html
[2]
https://lists.freebsd.org/pipermail/freebsd-hackers/2014-October/046181.html

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194279-8>