From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id n07EbtZK008183 for ; Wed, 7 Jan 2009 08:37:56 -0600 Received: from smtp5m5.poczta.onet.pl (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id CCC771B3455E for ; Wed, 7 Jan 2009 06:37:54 -0800 (PST) Received: from smtp5m5.poczta.onet.pl (smtp5m5.poczta.onet.pl [213.180.138.36]) by cuda.sgi.com with ESMTP id 18TC3eIrp3D0zDQM for ; Wed, 07 Jan 2009 06:37:54 -0800 (PST) Received: from ip-83-238-22-2.netia.com.pl ([83.238.22.2]:37050 "EHLO [192.168.242.3]" rhost-flags-OK-FAIL-OK-FAIL) by ps5.mod5.onet with ESMTPA id S251849908AbZAGOhvyi5Xp (ORCPT ); Wed, 7 Jan 2009 15:37:51 +0100 Message-ID: <4964BE38.8060007@poczta.onet.pl> Date: Wed, 07 Jan 2009 15:37:44 +0100 From: "aluno3@poczta.onet.pl" MIME-Version: 1.0 Subject: xfs_db problem List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com Hello, Recently we've noticed that xfs_admin (xfs_db ver. 2.10.2) causes segfault or FP traps while trying to use following command on FAT partition: # xfs_admin -u /dev/sda1 xfs_admin: unexpected XFS SB magic number 0xeb58906d Floating point exception and then makes error in dmesg: xfs_db[10385] trap divide error ip:80b32b0 sp:fffbd900 error:0 in xfs_db[8048000+7f000] We know that xfs_admin is dedicated tool for XFS only not for FAT or other filesystems, but we would like to have xfs_db which will be able to cope with non-xfs filesystems also. After some investigations we've found some place and put there exit(1) - in xfsprogs-2.10.2/db/init.c in init() procedure: (...) sbp = &xmount.m_sb; if (sbp->sb_magicnum != XFS_SB_MAGIC) { fprintf(stderr, _("%s: unexpected XFS SB magic number 0x%08x\n"), progname, sbp->sb_magicnum); exit(1); } (...) Is it the right way to fix this problem? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs