updatedb error

[Peter Reed]

I am receiving this error when I try to use the command updatedb:
updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
Aborted
however locate does seem to work although how old the database is unknown  any 
help with this would be appreciated.
Peter

[Vivek J. Patankar]

Peter Reed wrote:
> I am receiving this error when I try to use the command updatedb:
> updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
> Aborted
> however locate does seem to work although how old the database is unknown  any 
> help with this would be appreciated.

It seems that I am also having the same problem. I ran updatedb in 
verbose mode and the error comes with the same folder everytime. A 
listing of the folder gives strange output. Output from my terminal below.

/sys/module/nousb/parameters
  updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
  Aborted
  [root@marvin parameters]# file /sys/module/nousb/parameters
  /sys/module/nousb/parameters: directory
  [root@marvin parameters]# cd /sys/module/nousb/parameters
  [root@marvin parameters]# ls -l
  ls: cannot access : No such file or directory
  total 0
  -????????? ? ? ? ?                ?
  [root@marvin parameters]#

I tried rpm -qf to determine which package creates the folder but it 
says that the file is not owned by the package.

Can you run updatedb -v and check if the result is similar/identical?

[Peter Reed]

On Saturday 28 July 2007 6:09:50 pm Vivek J. Patankar wrote:
> Peter Reed wrote:
> > I am receiving this error when I try to use the command updatedb:
> > updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
> > Aborted
> > however locate does seem to work although how old the database is unknown
> >  any help with this would be appreciated.
>
> It seems that I am also having the same problem. I ran updatedb in
> verbose mode and the error comes with the same folder everytime. A
> listing of the folder gives strange output. Output from my terminal below.
>
> /sys/module/nousb/parameters
>   updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
>   Aborted
>   [root@marvin parameters]# file /sys/module/nousb/parameters
>   /sys/module/nousb/parameters: directory
>   [root@marvin parameters]# cd /sys/module/nousb/parameters
>   [root@marvin parameters]# ls -l
>   ls: cannot access : No such file or directory
>   total 0
>   -????????? ? ? ? ?                ?
>   [root@marvin parameters]#
>
> I tried rpm -qf to determine which package creates the folder but it
> says that the file is not owned by the package.
>
> Can you run updatedb -v and check if the result is similar/identical?
>
> --
> Regards,
> विवेक ज. पाटणकर (Vivek J. Patankar)
>
> Registered Linux User #374218
> Fedora release 7 (Moonshine)
> Linux 2.6.22.1-27.fc7 x86_64
> My USB drives automount! :p

Yes this is the same place my run of updatedb is exiting.  Same error as you 
with the same directory. 
Peter

[Vivek J. Patankar]

Peter Reed wrote:
> On Saturday 28 July 2007 6:09:50 pm Vivek J. Patankar wrote:
> > Peter Reed wrote:
> > > I am receiving this error when I try to use the command updatedb:
> > > updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
> > > Aborted
> > > however locate does seem to work although how old the database is unknown
> > >  any help with this would be appreciated.
> >
> > It seems that I am also having the same problem. I ran updatedb in
> > verbose mode and the error comes with the same folder everytime. A
> > listing of the folder gives strange output. Output from my terminal below.
> >
> > /sys/module/nousb/parameters
> >   updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
> >   Aborted
> >   [root@marvin parameters]# file /sys/module/nousb/parameters
> >   /sys/module/nousb/parameters: directory
> >   [root@marvin parameters]# cd /sys/module/nousb/parameters
> >   [root@marvin parameters]# ls -l
> >   ls: cannot access : No such file or directory
> >   total 0
> >   -????????? ? ? ? ?                ?
> >   [root@marvin parameters]#
> >
> > I tried rpm -qf to determine which package creates the folder but it
> > says that the file is not owned by the package.
> >
> > Can you run updatedb -v and check if the result is similar/identical?
>
> Yes this is the same place my run of updatedb is exiting.  Same error as you 
> with the same directory. 
> Peter

Can anybody else on the list verify this? What I would like to know is 
the contents of the directory. Listing the directory gives me strange 
output.

[inode0]

On 7/28/07, Vivek J. Patankar  wrote:
> Can anybody else on the list verify this? What I would like to know is
> the contents of the directory. Listing the directory gives me strange
> output.

I can confirm that it began with the 2.6.22 kernel on my system.

John

[Vivek J. Patankar]

inode0 wrote:
> On 7/28/07, Vivek J. Patankar  wrote:
> > Can anybody else on the list verify this? What I would like to know is
> > the contents of the directory. Listing the directory gives me strange
> > output.
>
> I can confirm that it began with the 2.6.22 kernel on my system.
>
> John

It seems it began sometime before that and a bug report was filed too.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242715

[Peter Reed]

On Saturday 28 July 2007 7:01:45 pm Vivek J. Patankar wrote:
> inode0 wrote:
> > On 7/28/07, Vivek J. Patankar  wrote:
> > > Can anybody else on the list verify this? What I would like to know is
> > > the contents of the directory. Listing the directory gives me strange
> > > output.
> >
> > I can confirm that it began with the 2.6.22 kernel on my system.
> >
> > John
>
> It seems it began sometime before that and a bug report was filed too.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242715
>
> --
> Regards,
> विवेक ज. पाटणकर (Vivek J. Patankar)
>
> Registered Linux User #374218
> Fedora release 7 (Moonshine)
> Linux 2.6.22.1-27.fc7 x86_64
> My USB drives automount! :p

I see from the bugzilla entry if you  --add-prunpaths /sys it works ok and I 
confirmed that it does.  Thanks for finding a temp work around .
Peter

[Mikkel]

Vivek J. Patankar wrote:
> Peter Reed wrote:
> > On Saturday 28 July 2007 6:09:50 pm Vivek J. Patankar wrote:
> > > Peter Reed wrote:
> > > > I am receiving this error when I try to use the command updatedb:
> > > > updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1'
> > > > failed.
> > > > Aborted
> > > > however locate does seem to work although how old the database is
> > > > unknown
> > > >  any help with this would be appreciated.
> > >
> > > It seems that I am also having the same problem. I ran updatedb in
> > > verbose mode and the error comes with the same folder everytime. A
> > > listing of the folder gives strange output. Output from my terminal
> > > below.
> > >
> > > /sys/module/nousb/parameters
> > >   updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1'
> > > failed.
> > >   Aborted
> > >   [root@marvin parameters]# file /sys/module/nousb/parameters
> > >   /sys/module/nousb/parameters: directory
> > >   [root@marvin parameters]# cd /sys/module/nousb/parameters
> > >   [root@marvin parameters]# ls -l
> > >   ls: cannot access : No such file or directory
> > >   total 0
> > >   -????????? ? ? ? ?                ?
> > >   [root@marvin parameters]#
> > >
> > > I tried rpm -qf to determine which package creates the folder but it
> > > says that the file is not owned by the package.
> > >
> > > Can you run updatedb -v and check if the result is similar/identical?
> >
> > Yes this is the same place my run of updatedb is exiting.  Same error
> > as you with the same directory. Peter
>
> Can anybody else on the list verify this? What I would like to know is
> the contents of the directory. Listing the directory gives me strange
> output.

The /sys file system is not a real file system - it is created as
part of udev, and contains information about hardware and drivers on
the running system. updatedb should not be checking this tree at
all. I wounder if /sys should be added to the PRUNEPATHS list in
/etc/updatedb.conf - that way the directory would be skipped.

Mikkel

[Vivek J. Patankar]

Mikkel L. Ellertson wrote:
> The /sys file system is not a real file system - it is created as
> part of udev, and contains information about hardware and drivers on
> the running system. updatedb should not be checking this tree at
> all. I wounder if /sys should be added to the PRUNEPATHS list in
> /etc/updatedb.conf - that way the directory would be skipped.

I added /sys and /proc in PRUNEPATHS in updatedb.conf.
Question is should we file an RFE for this to be part of defaults?

[Tim]

Vivek J. Patankar wrote:
> > > [root@marvin parameters]# cd /sys/module/nousb/parameters
> > >   [root@marvin parameters]# ls -l
> > >   ls: cannot access : No such file or directory
> > >   total 0
> > >   -????????? ? ? ? ?                ?
> What I would like to know is the contents of the directory. Listing
> the directory gives me strange output.

[root@bigblack ~]# cd /sys/module/nousb/parameters
[root@bigblack parameters]# ls -l
total 0
-r--r--r-- 1 root root 4096 2007-07-29 17:57 usbcore.autosuspend

[Vivek J. Patankar]

Tim wrote:
> > What I would like to know is the contents of the directory. Listing
> > the directory gives me strange output.
>
> [root@bigblack ~]# cd /sys/module/nousb/parameters
> [root@bigblack parameters]# ls -l
> total 0
> -r--r--r-- 1 root root 4096 2007-07-29 17:57 usbcore.autosuspend

You're using the latest kernel. I was using 2.6.22.1-27.fc7. I felt that 
upgrading the kernel could help. But no joy. The problem persists.

[Renich Bon Ciric]

On Sun, 2007-07-29 at 23:48 +0530, Vivek J. Patankar wrote:
> Tim wrote:
> > > What I would like to know is the contents of the directory. Listing
> > > the directory gives me strange output.
> >
> > [root@bigblack ~]# cd /sys/module/nousb/parameters
> > [root@bigblack parameters]# ls -l
> > total 0
> > -r--r--r-- 1 root root 4096 2007-07-29 17:57 usbcore.autosuspend
>
> You're using the latest kernel. I was using 2.6.22.1-27.fc7. I felt that 
> upgrading the kernel could help. But no joy. The problem persists.
>
> -- 
> Regards,
> विवेक ज. पाटणकर (Vivek J. Patankar)
>
> Registered Linux User #374218
> Fedora release 7 (Moonshine)
> Linux 2.6.22.1-33.fc7 x86_64
> My USB drives automount! :p

Same problem here. Has anybody generated a bug report?

[Vivek J. Patankar]

Renich Bon Ciric wrote:
> Same problem here. Has anybody generated a bug report?

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242715

Most of us who were facing the problem have added /sys to the PRUNEPATHS 
option in /etc/updatedb.conf.