Re: e2fsck
On Fri, 20 Oct 2006 18:30:14 +0200, Francesco Pietra wrote: > How to check the filesystem (ext3) if it is not mounted? umount /dev/whatever e2fsck -options /dev/whatever mount /dev/whatever -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsck
On Fri, Oct 20, 2006 at 05:47:52PM +, Francesco Pietra wrote: > Thanks a lot. Do these indications hold also for an external usb hd that is > shared with another machine? In fstab is presently dump 0, pass 0, so I have > to change to pass 1. If so, is it checked not-mounted at boot? > > Which options are used on automatic check? I refer to options for e2fsck, if > this applies to automatic check. > > Should I check the external usb hd manually by e2fsck (which, is I remember > correctly, for ext3 should only run the journal unless something very bad is > involved), which options are to be given? -p alone? I always just run fsck /dev/blah Let if figure out the fs itself. As for external drives, no I would not ask it to fsck those since most likely they are not set to mount automatically at boot. Those you can easily fsck before mounting them. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsck
On Friday 20 October 2006 16:37, Lennart Sorensen wrote: > On Fri, Oct 20, 2006 at 04:27:09PM +, Francesco Pietra wrote: > > A quick question related to > > > > "in general it is not safe to run e2fsck on mounted filesys- > >tems. The only exception is if the -n option is specified, and > > -c, -l, or -L options are not specified. However, even if it is safe > > to do so, the results printed by e2fsck are not valid if the filesystem > > is mounted.If e2fsck asks whether or not you should check a > > filesystem which is mounted, the only correct answer is ??no??. > > Only experts who really know what they are doing should consider > > answering this question in any other way" > > > > How to check the filesystem (ext3) if it is not mounted? > > > > That because I got warning that max count nr reached, suggesting to run > > e2fsck. > > I think the answer is: It is not safe to run fsck on a read-write > mounted filesystem, and if you run it on a read only filesystem, you > should unmount and remount it before making it readwrite. So for / you > really should run it while in read only mode, and then if any changes > were made, you reboot. This is how mine has always done it > automatically. > > To check filesystems automatically at boot when needed, set the check > flag in fstab. The last columns in fstab. I have all mine set to 1, > since linux fsck is smart enough to know not to run on multiple > partitions on one device at once. For raid systems it might be smarter > to stagger them if multiple raids share devices. The number is simply > which order to check the filesystems in, if they need checking. Thanks a lot. Do these indications hold also for an external usb hd that is shared with another machine? In fstab is presently dump 0, pass 0, so I have to change to pass 1. If so, is it checked not-mounted at boot? Which options are used on automatic check? I refer to options for e2fsck, if this applies to automatic check. Should I check the external usb hd manually by e2fsck (which, is I remember correctly, for ext3 should only run the journal unless something very bad is involved), which options are to be given? -p alone? Thanks again francesco pietra > > -- > Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade blows away /usr/bin?
Hi Henry, Henry Hollenberg wrote: > Still puzzling over how this happened. During the upgrade > I got a message about an install script not being able > to make a sym-link in /usr/X11R6/bin because > the directory was "full" and needed to be "emptied". I'm no X expert and maybe you would be better asking this on the [EMAIL PROTECTED] mailing list. But what I think happens during the upgrade is that, provided /usr/X11R6/bin is empty (maybe also if it's non-existent), the upgrade script rmdir's this directory and creates the symlink /usr/X11R6/bin -> /usr/bin . That is, it's not trying to make a symlink *in* /usr/X11R6/bin, it's trying to make a symlink *of* /usr/X11R6/bin. > So I moved it to /root/backup/usr_X11R6/bin where a copy > still resides. OK, so after that I'm guessing that you ran the upgrade script again and it was able to create the symlink (now that /usr/X11R6/bin either didn't exist or was empty). > before the final attempt at the upgrade I noticed a bunch > of files in /usr/X11R6/bin that weren't there before. Not > sure where they came from, I hadn't copied all those files > in there and I certainly hadn't done a sym-link. > > So I deleted them and finished the upgrade with no errors. > > Checked /usr/X11R6/bin and didn't see a symlink...uh-oh the > upgrade lied to me, what does that mean. Did you do "ls -l /usr/X11R6/bin" ? Because "ls -l /usr/X11R6/bin/" (note the trailing slash) would show you the directory contents even if /usr/X11R6/bin is itself a symlink. > Copied the saved copy back to /usr/X11R6/bin and went back > to work or tried to. > > That's when I noticed a whole lots of stuff wasn't working and > a whole lot of commands were MIA including "locate". > > Hmmm, > > checked /usr/bin and it held the contents of /usr/X11R6/bin > and did not have the 3000 some odd binaries and sym-links that > should be in there. > > That's kind of bad. > > So what happened, did I do an incredibly bone-headed thing? > Certainly possible, but I wonder if the upgrade scripts > somehow went up an extra level in the directory tree while > making a sym-link and fooled me. > > I'm pretty darn sure that the directory I was in was > /usr/X11R6/bin as I make a habit of doing a pwd before > doing an rm just do double check the what the system > prompt is telling me. If you used the shell's version of pwd, it is usually "smart" enough (at least this is the case for bash and zsh) to tell you your current directory relative to any symlinks into which you cd'ed. That is, if you cd into /usr/X11R6/bin but it is really a symlink to /usr/bin, typing "pwd" will still show you /usr/X11R6/bin. The "real" pwd, if you run it by typing "/bin/pwd", will show you that you are actually in /usr/bin. Sounds like you got hosed by some corner-case behavior of ls and pwd :-( Maybe you could send a report about this to debian-x and suggest that the upgrade process give a clear explanation of exactly what's going on? I'm glad to hear your next message sounds like you have mostly recovered: > Did a bunch of dpkg repair by hand and copied over some /usr/bin > files from another partition and apt finally took off. > > Still have lingering errors from postgresql and X is broken: > > andy:/etc/init.d# ./postgresql-7.4 restart > Restarting PostgreSQL 7.4 database server: main* Error: You must run this > program as the cluster owner (postgres) > failed! This sounds like a permissions problem; try to "aptitude reinstall" the package containing the postgresql-7.4 binary. (Or if aptitude is still broken because of this error, download the .deb and "dpkg -i" it by hand.) You can get a complete list of the installed packages that are supposed to have binaries in /usr/bin with "dpkg -S /usr/bin". It might be a good idea to "aptitude reinstall" all of them just to clear up any remaining inconsistencies. regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Jigdo download
On Fri, Oct 20, 2006 at 04:38:14PM +0100, Paul Tansom wrote: > I need to update my ISO in order to install onto a new motherboard that > has a nVidia nForce 430 chipset on it. I am hoping that the info on the > nVidia site is accurate in that they are now in the kernel tree > (including for AMD64!) so that I can manage the install (the main issue > is that I need to install onto RAID, so need the sata-nv driver > available at install time (I can work around the lack of the NIC drivers > as I have a second NIC installed). > I don't know anything about the amd64 Sarge stuff. However, I would guess that " in the kernel tree" doesn't mean in Sarge. I would suggest the daily-build of Etch, for amd64 if that's what you're using. I'm installing on a MB with nVidia nForce 570 and everything is detected automatically no problems, including the two GB-LAN ports. I'm installing onto raid1 with LVM, again no problem with the installer. I'm using the USB stick boot method with the business-card iso on it. Good luck. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsck
On Fri, Oct 20, 2006 at 04:27:09PM +, Francesco Pietra wrote: > A quick question related to > > "in general it is not safe to run e2fsck on mounted filesys- >tems. The only exception is if the -n option is specified, and -c, -l, >or -L options are not specified. However, even if it is safe to do >so, the results printed by e2fsck are not valid if the filesystem is >mounted.If e2fsck asks whether or not you should check a filesystem >which is mounted, the only correct answer is ??no??. Only > experts who >really know what they are doing should consider answering this question >in any other way" > > How to check the filesystem (ext3) if it is not mounted? > > That because I got warning that max count nr reached, suggesting to run > e2fsck. I think the answer is: It is not safe to run fsck on a read-write mounted filesystem, and if you run it on a read only filesystem, you should unmount and remount it before making it readwrite. So for / you really should run it while in read only mode, and then if any changes were made, you reboot. This is how mine has always done it automatically. To check filesystems automatically at boot when needed, set the check flag in fstab. The last columns in fstab. I have all mine set to 1, since linux fsck is smart enough to know not to run on multiple partitions on one device at once. For raid systems it might be smarter to stagger them if multiple raids share devices. The number is simply which order to check the filesystems in, if they need checking. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e2fsck
A quick question related to "in general it is not safe to run e2fsck on mounted filesys- tems. The only exception is if the -n option is specified, and -c, -l, or -L options are not specified. However, even if it is safe to do so, the results printed by e2fsck are not valid if the filesystem is mounted.If e2fsck asks whether or not you should check a filesystem which is mounted, the only correct answer is ‘‘no’’. Only experts who really know what they are doing should consider answering this question in any other way" How to check the filesystem (ext3) if it is not mounted? That because I got warning that max count nr reached, suggesting to run e2fsck. Thank you francesco pietra
AMD64 Jigdo download
Before I delve too far into the problem I thought I'd just venture a quick post to see if there is a known problem with the Debian AMD64 Jigdo files that are listed at: http://cdimage.debian.org/cdimage/unofficial/sarge-amd64/jigdo-cd/ I need to update my ISO in order to install onto a new motherboard that has a nVidia nForce 430 chipset on it. I am hoping that the info on the nVidia site is accurate in that they are now in the kernel tree (including for AMD64!) so that I can manage the install (the main issue is that I need to install onto RAID, so need the sata-nv driver available at install time (I can work around the lack of the NIC drivers as I have a second NIC installed). Anyway, when I download using Jigdo I get 211 files that aren't available. I have manually ftp'd in and confirmed that they are not (well one or two) on the UK, ticklers and main .org ftp sites. My suspicion is that they've not been kept as up to date as the ftp site since one of the files (kernel headers iirc - sorry not at the correct machine at present) has a more up to date version that the one it is trying to download. If it is relevant I can supply more details, but didn't feel it worth doing at this early 'quick check' stage. -- Paul Tansom | Aptanet Ltd. | http://www.aptanet.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: MB Asus M2N32 SLI Deluxe WiFi Edition and Dedian/GNU
On Fri, Oct 20, 2006 at 12:39:01PM +0200, Thierry Chatelet wrote: > Well, thanks all for your answers. My main concern was about the 2 lans > and the wifi ship. Sound is not an issue, would still be nice to have it > working, but as long as the rest is working, it's OK. Well most nforce ethernet chips have ended up working rather quickly. I am not sure which one is on that board. According to nvidia forcedeth version 0.56 should work with all current nvidia chipsets. The version in 2.6.16 is 0.49, 0.56 was added in 2.6.18, and I think 0.54 was added in 2.6.17. 0.56 added support for the MCP6x series by the looks of it. The wifi probably won't work unless they happend to pick one of the few that actually has linux support (ndiswrappers don't count in my opinion since they break too often and are a real pain in the @$$ to get working). I wouldn't get my hopes up. Unfortunately asus doesn't tell you waht type of wireless chip they use, other than the interface to it is usb based. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: MB Asus M2N32 SLI Deluxe WiFi Edition and Dedian/GNU
C_Wakefield wrote: It works! Thanks Stephen, I knew there would be a way to do this. Best Regards, Chris W. On Thursday 19 October 2006 18:48, Stephen Cormier wrote: On Thursday 19 October 2006 21:55, C_Wakefield wrote: Had trouble with the temperature sensors (on-chip k8_temp) until I realized that the current 2.6.16-2-amd64-k8-smp debian kernel doesn't have support for it (k8_temp) so I'm running without knowing the cpu(s) temperatures. Try compiling the module in the URL below then with the 2.10.1 version of lm-sensors/libsensors3 the temperatures will show up in the sensors command. http://assembler.cz/download/amd_digital_temp.tar.gz Stephen Well, thanks all for your answers. My main concern was about the 2 lans and the wifi ship. Sound is not an issue, would still be nice to have it working, but as long as the rest is working, it's OK. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
