Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Repairing\s+a\s+possibly\s+incomplete\s+xfs_growfs\s+command\?\s*$/: 44 ]

Total 44 documents matching your query.

1. Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Wed, 16 Jan 2008 15:19:19 -0800
So I have run across a strange situation which I hope there are some gurus out there to help. The original setup was a logical volume of 8.9TB. I extended the volume to 17.7TB and attempted to run x
/archives/xfs/2008-01/msg00085.html (9,425 bytes)

2. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Wed, 16 Jan 2008 20:31:08 -0600
hm, how big is your block device for starters - look in /proc/partitions. -Eric
/archives/xfs/2008-01/msg00088.html (9,959 bytes)

3. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 14:01:11 +1100
Hmmm - what kernel and what version of xfsprogs are you using? (xfs_growfs -V). Also, can you post the output of the growfs command if you still have it? If not, the output of: xfs_db -r -c 'sb 0' -c
/archives/xfs/2008-01/msg00090.html (11,062 bytes)

4. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 09:29:22 -0800
Of volume the was data sure xfs_growfs version 2.9.4 magicnum = 0x58465342 blocksize = 4096 dblocks = 11904332800 rblocks = 0 rextents = 0 uuid = 05d4f6ba-1e9c-4564-898b-98088c163fe1 logstart = 2147
/archives/xfs/2008-01/msg00091.html (14,377 bytes)

5. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 13:10:42 -0600
are those two assembled into your actual block device? They look each about 8T. Is the lvm device also in /proc/partitions? -Eric
/archives/xfs/2008-01/msg00092.html (9,911 bytes)

6. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 12:04:47 -0800
Here's the entire output: major minor #blocks name 3 0 512000 hda 3 1 511528 hda1 152 0 9523468862 etherd/e1.0 152 16 9523468862 etherd/e0.0 254 0 19046932480 dm-0 I believe dm-0 is the lvm device.
/archives/xfs/2008-01/msg00093.html (10,907 bytes)

7. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 16:19:59 -0600
Yep, in 1k units, so: 19046932480*1024 19504058859520 and: superblock read failed, offset 19504058859520, size 2048, ag 64, rval 0 so it's trying to read a 2k (?) superblock right in the last 1k of t
/archives/xfs/2008-01/msg00094.html (10,640 bytes)

8. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Fri, 18 Jan 2008 09:47:34 +1100
sectsize = 512 sectlog = 9 So, SB reckons its a regular 512 byte sector size. Perhaps the device driver is reporting a 2K sector size from the BLKSSZGET ioctl? That'd be wierd, cos mkfs would have is
/archives/xfs/2008-01/msg00095.html (11,303 bytes)

9. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Fri, 18 Jan 2008 10:15:17 +1100
Ok, that's recent - what kernel? (uname -a) = 44TB? .... = ~283GB 160*283GB = 44TB. Hold on - 160 AGs? I saw this exact same growfs failure signature just before Christmas at a customer site on an ol
/archives/xfs/2008-01/msg00096.html (14,351 bytes)

10. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Thu, 17 Jan 2008 15:29:17 -0800
4761733120' This is quite a relief to know that this is a fairly straightforward fix! What luck that you had encountered it recently, I really appreciate the help. Here's my uname output: Linux pure
/archives/xfs/2008-01/msg00097.html (17,283 bytes)

11. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Fri, 18 Jan 2008 10:46:04 +1100
/me breathes a sigh of relief I think we have: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=20f4ebf2bf2f57c1a9abb3655391336cc90314b3 [XFS] Make growfs work for amounts
/archives/xfs/2008-01/msg00098.html (12,062 bytes)

12. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Fri, 18 Jan 2008 09:50:37 -0800
Is this supposed to be the proper output to the command above? purenas:~# for i in `seq 0 1 63`; do xfs_db -x -c "sb $i" -c 'write agcount 64' -c 'write dblock 4761733120' /dev/vg0/lv0; done agcount
/archives/xfs/2008-01/msg00114.html (14,387 bytes)

13. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Fri, 18 Jan 2008 12:34:31 -0600
... I think dave had a typo, should be dblocks with an "s" on the end. Feel free to wait for his confirmation, though, since this is surgery, after all :) -eric
/archives/xfs/2008-01/msg00116.html (11,309 bytes)

14. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Sat, 19 Jan 2008 11:40:18 +1100
Ah - As eric pointed out, that should be "dblocks". Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group
/archives/xfs/2008-01/msg00119.html (11,209 bytes)

15. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Tue, 22 Jan 2008 11:40:52 -0800
fixed Any ideas on how long the xfs_repair is supposed to take on 18TB? I started it Friday nite, and it's now Tuesday afternoon. It's stuck here: Phase 5 - rebuild AG headers and trees... - reset s
/archives/xfs/2008-01/msg00179.html (12,392 bytes)

16. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Wed, 23 Jan 2008 08:13:11 +1100
Yes, it can if it's swapping like mad because you don't have enough RAM in the machine. Runtime is also detemrined by how many inodes there are in the filesystem - do you know how many there are? Als
/archives/xfs/2008-01/msg00181.html (11,093 bytes)

17. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Tue, 22 Jan 2008 13:46:56 -0800
Of days there Using version 2.9.4. I may have forgotten to allocate more swap space (as was told in the manual given to me by the vendor), so would breaking out of the repair and restarting with mor
/archives/xfs/2008-01/msg00182.html (12,156 bytes)

18. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Wed, 23 Jan 2008 09:48:18 +1100
Mark Magpayo wrote: --Original Message-- From: xfs-bounce@xxxxxxxxxxx [mailto:xfs-bounce@xxxxxxxxxxx] On Behalf Of David Chinner Sent: Tuesday, January 22, 2008 1:13 PM To: Mark Magpayo Cc: xfs@xxxxx
/archives/xfs/2008-01/msg00183.html (13,463 bytes)

19. RE: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Tue, 22 Jan 2008 14:50:39 -0800
Of Behalf I stuck space breaking too Here you go: purenas:~# cat /proc/meminfo MemTotal: 1019732 kB MemFree: 580920 kB Buffers: 1720 kB Cached: 17912 kB SwapCached: 21712 kB Active: 44016 kB Inactiv
/archives/xfs/2008-01/msg00184.html (14,074 bytes)

20. Re: Repairing a possibly incomplete xfs_growfs command? (score: 1)
Author:
Date: Wed, 23 Jan 2008 13:57:37 +1100
On Wed, 23 Jan 2008 06:40:52 +1100, Mark Magpayo <mmagpayo@xxxxxxxxxxxxx> --Original Message-- From: David Chinner [mailto:dgc@xxxxxxx] Sent: Friday, January 18, 2008 4:40 PM To: Mark Magpayo Cc: Dav
/archives/xfs/2008-01/msg00188.html (12,727 bytes)


This search system is powered by Namazu