| To: | Jan Derfinak <ja@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: can't seek in filesystem at bb 8207728640 |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Sat, 8 Feb 2003 08:06:55 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.44.0302062330200.24227-100000@alienAngel.home.sk>; from ja@mail.upjs.sk on Fri, Feb 07, 2003 at 10:46:44AM +0100 |
| References: | <Pine.LNX.4.44.0302062330200.24227-100000@alienAngel.home.sk> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Feb 07, 2003 at 10:46:44AM +0100, Jan Derfinak wrote:
> Hi all.
hi there,
> # xfs_db -r /dev/hda8
> xfs_db: freesp
> can't seek in filesystem at bb 8207728640
> can't read btree block 0/1025966080
> can't seek in filesystem at bb 29141501952
> can't read btree block 0/3642687744
> ...
> I found this message on one of my xfs partions. Please can anybody explain
> me that?
It is almost certainly an xfs_db bug that was fixed recently.
> How dangerous is that for my data?
Not dangerous, its likely to be a problem in xfs_db, so not on-disk.
> xfs_db is from xfsprogs-2.3.6
Try xfsprogs-2.3.7, from xfsprogs/doc/CHANGES...
xfsprogs-2.3.7 (14 November 2002)
- Fix an endian bug in xfs_db freesp command when descending
into multi-level agf cnt/bno btrees.
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | maxiosz value, Gabor Forgacs |
|---|---|
| Next by Date: | [Bug 206] XFS filesysem corruption while umounting sw raid 1, bugzilla-daemon |
| Previous by Thread: | Re: can't seek in filesystem at bb 8207728640, Jan Derfinak |
| Next by Thread: | Re: can't seek in filesystem at bb 8207728640, Jan Derfinak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |