Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Map\s+a\s+disk\s+LBA\s+to\s+filename\?\s*$/: 48 ]

Total 48 documents matching your query.

1. tter (score: 1)
Author: o@xxxxxxxxx>
Date: Mon, 27 Oct 2008 12:20:27 +0100
Hi all, I have not found it in the archive, thus my question to all: Along the lines of this doc http://smartmontools.sourceforge.net/BadBlockHowTo.txt I would like to find out if that's also possibl
/archives/xfs/2008-10/msg00590.html (9,027 bytes)

2. t xfs (score: 1)
Author: @xxxxxxxxxx>
Date: Mon, 27 Oct 2008 22:49:45 +1100
Use xfs_bmap to find the location on disk of the extents in each file. Recurse over the filesystem until you find the file that owns the block that went bad. Cheers, Dave. -- Dave Chinner david@xxxxx
/archives/xfs/2008-10/msg00591.html (9,697 bytes)

3. ories (score: 1)
Author: xxxxxxxxxxx>
Date: Mon, 27 Oct 2008 13:31:06 +0100
Hi Dave (and Peter) Sounds like a tedious but doable route to take. Thanks for the quick reply! Carsten
/archives/xfs/2008-10/msg00594.html (8,671 bytes)

4. elect first log item to push (score: 1)
Author: xxxxxxxxxxx>
Date: Mon, 27 Oct 2008 14:03:15 +0100
Carsten Aulbert wrote: Dave Chinner wrote: Use xfs_bmap to find the location on disk of the extents in each file. Recurse over the filesystem until you find the file that owns the block that went bad
/archives/xfs/2008-10/msg00600.html (9,490 bytes)

5. H 5/6] kill the XFS_IMAP_BULKSTAT flag (score: 1)
Author: xxxxxxxxxxx>
Date: Mon, 27 Oct 2008 14:54:35 +0100
Hi Michal Sounds nice, but my (ancient? 2.8.11) version of xfs_db does not know getblock (only blockget) since that also matches the command line and the usage looks about to be right, I'm currently
/archives/xfs/2008-10/msg00640.html (9,987 bytes)

6. T flag (score: 1)
Author: @xxxxxxxxxx>
Date: Mon, 27 Oct 2008 16:56:34 +0100
Carsten Aulbert wrote: Michal Soltys wrote: Wouldn't something like (under xfs_db) : getblock -b #block -n ncheck -i #inode where required #inode is reported by getblock do the thing ? Sounds nice, b
/archives/xfs/2008-10/msg00641.html (11,728 bytes)

7. ] remove dead code from sv_t implementation (score: 1)
Author: all@xxxxxxx>
Date: Tue, 28 Oct 2008 10:35:16 +1100
Blockget - yes it will. It just does the traversal internally to build the mapping. With large filesystems xfs_db can run out of memory building the mapping, which is why I've used the explicit trave
/archives/xfs/2008-10/msg00645.html (10,434 bytes)

8. d day with xfsrestore, what went wrong? (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 08:11:46 +0100
Hi Dave et al How expensive is this operation (rule of thumb)? We will mostly use this on compute nodes where the partition is 500-750 GB large and the node has 8 GB of memory. For the simple test wh
/archives/xfs/2008-10/msg00667.html (9,707 bytes)

9. use inode_change_ok for setattr permission checking (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 18:21:05 +1100
Shouldn't be a problem with a filesystem that size. It's when you're dealing with tens of terabytes in a single filesystem that it can be a problem... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxx
/archives/xfs/2008-10/msg00670.html (10,652 bytes)

10. permission checking (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 08:38:12 +0100
It used a bit less than 900MB, so no problem at all. But I think I'm a bit stuck now, because I know not enough about the conventions used: meta-data=/dev/sda6 isize=256 agcount=16, agsize=7388267 bl
/archives/xfs/2008-10/msg00671.html (10,938 bytes)

11. - kill sys_cred (score: 1)
Author: @xxxxxxxxxx>
Date: Tue, 28 Oct 2008 08:52:31 +0100
* Carsten Aulbert (carsten.aulbert@xxxxxxxxxx) [20081028 08:38]: xfs_bmap(8) talks in basic blocks (512 bytes). 847868600*512 < 118212272*4096. HTH, Peter -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kele
/archives/xfs/2008-10/msg00672.html (10,247 bytes)

12. on (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 10:14:55 +0100
Related, more logical errors on my side probably: Can someone give me a hint what I'm doing wrong here? xfs_bmap -l /local/boinc/time_stats_log /local/boinc/time_stats_log: 0: [0..127]: 280..407 128
/archives/xfs/2008-10/msg00675.html (10,837 bytes)

13. mplement generic freeze feature (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 10:38:27 +0100
* Carsten Aulbert (carsten.aulbert@xxxxxxxxxx) [20081028 10:14]: xfs_bmap(8) talks in basic blocks (512 bytes). 660 div 8 = 82, so try: blockget -b 82 -n [...] All the file offsets and disk block
/archives/xfs/2008-10/msg00677.html (10,344 bytes)

14. Re: deadlock with latest xfs (score: 1)
Author: men@xxxxxxx>
Date: Tue, 28 Oct 2008 05:52:29 -0400 (EDT)
On Tue, 28 Oct 2008, KELEMEN Peter wrote: * Carsten Aulbert (carsten.aulbert@xxxxxxxxxx) [20081028 10:14]: Is it possible that blocks != bsized_blocks? xfs_bmap(8) talks in basic blocks (512 bytes).
/archives/xfs/2008-10/msg00678.html (11,047 bytes)

15. [PATCH 4/7] kill xfs_ialloc_log_di (score: 1)
Author: xxxxxxxxxxx>
Date: Tue, 28 Oct 2008 10:51:58 +0100
Carsten Aulbert wrote: Carsten Aulbert wrote: Any idea where my logical error is? Related, more logical errors on my side probably: Can someone give me a hint what I'm doing wrong here? xfs_bmap -l /
/archives/xfs/2008-10/msg00679.html (12,280 bytes)

16. ioctl (score: 1)
Author: in <markgw@xxxxxxx>
Date: Thu, 30 Oct 2008 16:23:09 +1100
I think all of you need to know about the "convert" command ;) e.g. to do the above conversion correctly: 0x52 (82) The xfs_db man page tells you all the different formats that can be converted betwe
/archives/xfs/2008-10/msg00734.html (10,098 bytes)

17. t (score: 1)
Author: gan dawit" <ari.poljo@xxxxxxxxx>
Date: Mon, 27 Oct 2008 12:20:27 +0100
Hi all, I have not found it in the archive, thus my question to all: Along the lines of this doc http://smartmontools.sourceforge.net/BadBlockHowTo.txt I would like to find out if that's also possibl
/archives/xfs/2008-10/msg01448.html (8,848 bytes)

18. inode reclaim path (score: 1)
Author: ert <carsten.aulbert@xxxxxxxxxx>
Date: Mon, 27 Oct 2008 22:49:45 +1100
Use xfs_bmap to find the location on disk of the extents in each file. Recurse over the filesystem until you find the file that owns the block that went bad. Cheers, Dave. -- Dave Chinner david@xxxxx
/archives/xfs/2008-10/msg01449.html (9,518 bytes)

19. (score: 1)
Author: ve Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 27 Oct 2008 13:31:06 +0100
Hi Dave (and Peter) Sounds like a tedious but doable route to take. Thanks for the quick reply! Carsten
/archives/xfs/2008-10/msg01452.html (8,492 bytes)

20. ags (score: 1)
Author: toph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 27 Oct 2008 14:03:15 +0100
Carsten Aulbert wrote: Dave Chinner wrote: Use xfs_bmap to find the location on disk of the extents in each file. Recurse over the filesystem until you find the file that owns the block that went bad
/archives/xfs/2008-10/msg01458.html (9,307 bytes)


This search system is powered by Namazu